Yes, enable it on the server. Only records with old timestamps will be deleted. So the only real possible negative is you somehow have "valid" records with old timestamps that have not been refreshing their timestamps for some reason. How could that happen? Perhaps you had devices previously performing dynamic updates but then someone disabled the feature on them so now their records have old timestamps.
Don't worry about the "set all zones..." option unless you want to enable scavenging on all the zones by default. To your 3rd and 4th questions, yes and yes. Just make sure you have valid backups and flip the switch. Just because it's the day before a major holiday doesn't mean you can't take risks. :) You can also use dnscmd.exe /zoneexport to dump the zone(s) if you want a file backup of it. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gordon Pegue Sent: Wednesday, November 22, 2006 10:58 AM To: [email protected] Subject: [ActiveDir] DNS Scavenging - new issue The recent thread on DNS scavenging was interesting and informative. It has lead me to investigate my own DNS scavenging issue and I'd appreciate some assistance with figuring out how to resolve it. I manage a single domain with a mixture of 2 - Win2K & 3 - Win2K3 servers. My 2 DC's are on Win2K boxes, I have one Win2K3 server running Exchange 2K3 and the other 2 Win2K3 servers are basically file servers at this point although we plan on promoting one to a DC in the near future and retiring one of the Win2K DC's. My DNS is AD integrated. My issue involves the issue of old, stale DNS RR's not being properly scavenged and even though I've read some of the documents linked in the previous thread, I'm still a bit uncertain how to rectify my issue without totally botching things - I'm a bit of a newbie... Anyhow, I examine the contents of my Reverse Lookup Zone and I find 2 Name entries for the same machine name. If I examine the properties of each, I see, for example, that the Record Time Stamp for one is 6-6-05 and 11-21-06 for the other. Checking DHCP shows that the IP address for the 11-21-06 entry is the active one. When I check the Aging settings for the zone, I see that the No-refresh interval is set to 7 hours, the Refresh interval is set to 7 days and the Scavenge stale RR check box is checked. OK so far, me thinks. When I check the properties for the DNS server, under the Advanced tab, the Enable automatic scavenging of stale records check box is _not_ checked. My first question: Should it be checked? My second question: Are the any negative consequences to doing so? Next, when I right-click the DNS server and click Set Aging/ Scavenging for All Zones, I see that the No-refresh interval is set to 7 days, the Refresh interval is also set to 7 days and the Scavenge stale RR check box is _not_ checked. My third question: As opposed to my previous 2 questions, is this where I should be enabling scavenging? My final question: Once the scavenging has been properly enabled, will the really stale RR records be removed? TIA Gordon Pegue List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/[email protected]/ List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/[email protected]/
