I went through and read this article: hXXp://blogs.technet.com/b/networking/archive/2008/03/19/don-t-be-afraid-of-dns-scavenging-just-be-patient.aspx
(it wouldnt let me post a link, change the xx to tt)
My scenario is a bit different as the server was setup with no Aging/Scavenging except on the Forward Lookup Zone, which was set to 14 days Refresh/No Refresh. The DHCP, of course, was set to a lease of 8 days, so this wasn't working. I've swapped it to 7/7 respectively since the lease default of 8 is staying in place.
There are records in there from long before 2011 (some going back as far as 2008), and when you go into the Zone Aging/Scavenging Properties, the Date and time listed for when the zone can be scavenged is 4/26/2011. I have reloaded the zone, and it still remains the same.
In the Reverse Lookup Zones, no Aging/Scavenging was even defined/enabled.
I want to enable Aging/Scavenging for all zones to be 7/7 in respect for the DHCP lease remaining the default 8 day lease.
I suppose my question is--why isn't the date for when things will be scavenging updating to a future date instead of remaining the previous date of 4/26/2011, and also, is there any reason why setting 7/7 across all zones would cause any issues?
I plan to obviously wait the 2 weeks and then do the 'sanity check' before going through with the removals.