DNS issues with old time stamps

So I inherited a domain that's 15 years old.  It's DNS has NEVER been scavenged or cleaned up to speak of and it's showing.  I have records with time stamps of tens years ago, five years ago, etc.  I also have multiple A records for DNS names associated with the same IP.  It's generally messy.

In my start to cleaning it up, my first issue is that apparently my PCs and servers are not refreshing properly.  Here's why I say that.

I have a server that is in production and it answers pings.  It of course has a statically assigned IP address.  In DNS, it has a time stamp, which I understand, but the time stamp is seven years old.  I expected that when the server refreshed, the time stamp would update, BUT, have no scavenging settings set, so maybe that's why no refresh.  If I turn on scavenging, I'll lose servers with old time stamps when in reality, they are active.

So, can anyone tell me why I have servers with five year old time stamps that are not refreshed?  I mean I expect the servers to refresh their live status and DNS to change the time stamp.

Thanks!
crp0499CEOAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Will SzymkowskiSenior Solution ArchitectCommented:
Static "Timestamp" addresses are automatically filtered out of the Scavenging and Aging process. All other records that are Dynamic "should" automatically update their timestamp (static or dynamic) use the DNS Client Service to update their DNS timestampe.

What you can do is try ipconfig /registerdns command and see if the timestamp changes.

Will.
crp0499CEOAuthor Commented:
Will, are you telling me those servers with those old time stamps will not be removed based on the time stamp?
Will SzymkowskiSenior Solution ArchitectCommented:
If you enable Scavenging those servers will get removed if the timestamp is outside of what you have set  for the scavenging parameters.

I am saying go to those servers that have "out of date" timestamps and run ipconfig /registerdns to see if it updates the DNS recrods on the server.

I would do that before considering enabling this feature.

Will.
Starting with Angular 5

Learn the essential features and functions of the popular JavaScript framework for building mobile, desktop and web applications.

crp0499CEOAuthor Commented:
It DID update it's time stamp.
Will SzymkowskiSenior Solution ArchitectCommented:
As long as the timestamp is outside of the scavanging and aging it will not remove these entries.

Will.
footechCommented:
I almost always provide this link to someone with questions about scavenging.  It is very comprehensive.
http://blogs.technet.com/b/networking/archive/2008/03/19/don-t-be-afraid-of-dns-scavenging-just-be-patient.aspx

If you don't have aging settings configured on a zone, timestamps won't replicate, so your view could be different on different DCs.

For more info about how dynamic DNS, DHCP, and scavenging all relate, I also recommend:
http://blogs.technet.com/b/askpfe/archive/2011/06/03/how-dns-scavenging-and-the-dhcp-lease-duration-relate.aspx
http://blogs.msmvps.com/acefekay/2009/08/20/dhcp-dynamic-dns-updates-scavenging-static-entries-amp-timestamps-and-the-dnsproxyupdate-group/

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
crp0499CEOAuthor Commented:
I'm thinking as a fix, running a powershell to force every PC/Server on the domain to re register in DNS and then turn on scavenging.  

Thoughts Will and footech?
footechCommented:
That's fine.  But as mentioned in the first link I gave, don't be in a rush.  You can run the command to force a machine to register, but what you really want to do is monitor the situation and verify that machines are automatically updating their records going forward.  Otherwise sometime in the future records will be scavenged that you don't want (though often the situation will clear up when the client registers again).  It's also good to note that when you have clients that hop around and change IPs, you will have periods where the record isn't up-to-date, but with scavengening these will cleared up so they don't hang around too long.
crp0499CEOAuthor Commented:
Foo, what i don't understand is that live, active machines are not refreshing their time stamps at reboot, etc.  I have machines with seven year old time stamps.  THAT concerns me.
footechCommented:
Ownership of an existing record could be blocking some clients from updating a record.

And we haven't gone through what your aging settings are for zones, what your dynamic update settings are, etc.  That's the why for the recommended reading, so you can better understand all these interactions.  Group Policy and NIC settings are also available that can change update behavior.
crp0499CEOAuthor Commented:
ok, I'll run with what I have then.  Thanks buddy!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DNS

From novice to tech pro — start learning today.