Dns server is not updating
If there are missing entries, you likely have your DHCP missing one of two settings: This is required if you have DHCP installed on a Domain Controller.It is an issue on Server 2000, 2003, 2008, 2008R2, Server 2012, Server 2012 R2 and will likely be an issue in the newer builds.After the (Record Timestamp) (No-refresh interval) elapses we enter the Refresh interval.The refresh interval is the time when refreshes to the timestamp are allowed. The client is allowed to come in and update it’s timestamp.This timestamp will be replicated around and the No-refresh interval begins again.If for some reason the client fails to update it’s record during the refresh interval it becomes One last thing before we leave the zone setting behind.The “zone can be scavenged after” timestamp is the first of your safety valves.
Windows clients will attempt to dynamically update DNS every 24 hours. When a record is first created by a client that has no existing record it is considered an “Update” and the timestamp is set.The purpose of a No-refresh interval is simply to reduce replication traffic.A change to a record means a change that must be replicated.Remember that old test server that you built two years ago that caught fire before it could be used? We’ll go through how scavenging is setup then I’ll give you my best practices.Scavenging will help you clean up old unused records in DNS.