DNS Stale Record Scavageing and DHCP Reservations "Michael D. Ober" <obermd.[ at ].alum.mit.edu.nospam.> 10/1/2008 11:25:50 PM I have a DHCP server that sets the lease to 31 days and also has several reservations as well as dynamic updates to DNS. This morning I discovered that some of the reservations had had their A records removed from DNS via the DNS scavenge for stale records feature, effectively hiding the devices from the network (they still worked via IP, but name resolution failed). Server is Windows 2003 R2 SP2 running MS AD Authorized DHCP and AD integrated DNS. My question is can I use the DNS stale record scavenge features in this configuration, and if so, what values do I need to give my DNS server to avoid scavenging my DHCP reservations? Thanks in Advance, Mike Ober.

RE: DNS Stale Record Scavageing and DHCP Reservations James. 10/2/2008 9:08:10 PM Hi there, 31 days is a rather long time to set DHCP leases and its generally best to leave it to the default 8 day lease. Saying that what you are trying to do is feasible. In DNS management, on the ZONE you need to leave the no-refresh interval at 7 days and then change the refresh interval to 24 days (or some other combination that adds to 31). That way the record cannot be scavenged for 31 days after it is created. -- James Yeomans, BSc, MCSE "Michael D. Ober" wrote: [Quoted Text] > I have a DHCP server that sets the lease to 31 days and also has several > reservations as well as dynamic updates to DNS. This morning I discovered > that some of the reservations had had their A records removed from DNS via > the DNS scavenge for stale records feature, effectively hiding the devices > from the network (they still worked via IP, but name resolution failed). > Server is Windows 2003 R2 SP2 running MS AD Authorized DHCP and AD > integrated DNS. > > My question is can I use the DNS stale record scavenge features in this > configuration, and if so, what values do I need to give my DNS server to > avoid scavenging my DHCP reservations? > > Thanks in Advance, > Mike Ober. > > >

Re: DNS Stale Record Scavageing and DHCP Reservations "Michael D. Ober" <obermd.[ at ].alum.mit.edu.nospam.> 10/2/2008 10:52:20 PM James, thanks. I set the DHCP to 31 because the network has plenty of address space and a relatively slow machine life cycle. Thanks. Mike "James." <James[ at ]discussions.microsoft.com> wrote in message news:9A6995E2-A480-4334-92E7-14B33FDCB00E[ at ]microsoft.com... [Quoted Text] > Hi there, 31 days is a rather long time to set DHCP leases and its > generally > best to leave it to the default 8 day lease. Saying that what you are > trying > to do is feasible. > In DNS management, on the ZONE you need to leave the no-refresh interval > at > 7 days and then change the refresh interval to 24 days (or some other > combination that adds to 31). That way the record cannot be scavenged for > 31 > days after it is created. > -- > James Yeomans, BSc, MCSE > > > "Michael D. Ober" wrote: > >> I have a DHCP server that sets the lease to 31 days and also has several >> reservations as well as dynamic updates to DNS. This morning I >> discovered >> that some of the reservations had had their A records removed from DNS >> via >> the DNS scavenge for stale records feature, effectively hiding the >> devices >> from the network (they still worked via IP, but name resolution failed). >> Server is Windows 2003 R2 SP2 running MS AD Authorized DHCP and AD >> integrated DNS. >> >> My question is can I use the DNS stale record scavenge features in this >> configuration, and if so, what values do I need to give my DNS server to >> avoid scavenging my DHCP reservations? >> >> Thanks in Advance, >> Mike Ober. >> >> >> >