I am trying to implement DNS scavenging in my Active Directory integrated DNS environment, but I have a weird situation occurring. All stale PTR records are being scavenged properly from the reverse lookup zones, but the stale A records in my primary forward lookup zone stubbornly remain. My environment contains 3 DNS servers- 2 Windows Server 2003 Standard Edition SP2 DC's and a single Windows Server 2008 R2 SP1 DC.
Here is what I have done so far:
1. Enabled aging/scavenging on all of the zones I wish to scavenge on the DNS servers
2. I watched over the next several weeks to see how the timestamps were replicated around the DC's and made sure that all of my critical systems were updating as expected so that they would not be accidentally deleted.
3. The zones in question were eligible to be scavenged several weeks ago according to DNS
4. I proceeded to enable scavenging on the Windows Server 2008 R2 SP1 DC/DNS server and set it to scanvenge the stale resource at the default interval of 7 days
5. In order to make an immediate scavenging pass, I manually initiated a scavenging operation on the DC mentioned in step 4 above.
6. The results were that all of the stale records in the multiple reverse zones were immediately scavenged as expected. However, all of the stale resource records in the forward lookup zone remain and will not be removed no matter where I run the manual scavenge from.
7. I checked the security tab on the records in both types of zones and everything is identical
My question here is - what am I missing? I followed this article as exactly as possible, but perhaps I have overlooked some nuance:
All of the stale A records are set to be scavenged when they become stale (checkbox on the record itself) and all of them are very VERY old 7/1/2009 for example. Scavenging is enabled in all three places - the DNS server, the zone in question, and the individual A record.
Perhaps my best bet is just to manually delete all of the old A records from the forward lookup zone and then watch the behavior with all newly created dynamic A records moving forward? Could it be something with the mix of 2003 and 2008 R2 DNS servers?
Any ideas? Please don't ask if I have enabled scavenging on the DNS server as well as the individual zones. That is the canned answer that appears over and over on technet and google as a response to this problem. I came to Experts Exchange with this issue for a reason! ;-)
Thanks in advance,