If you are working with, well almost anything network intensive these days, like Antivirus or management tools, your Reverse DNS (r DNS) lookups need to be in good shape.
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.
If you check your servers event viewer you will see EVENT ID 1056: The DHCP service has detected that it is running on a DC and has no credentials configured for use with Dynamic DNS registrations initiated by the DHCP service. Credentials for Dynamic DNS registrations may be configured using the command line “netsh dhcp server set dnscredentials” or via the DHCP Administrative tool.
I set this back to 7 days, in an attempt to give DNS a chance to 'catch up' before the addresses potentially changed again, but we're still getting incorrect DNS entries. Our settings are now an amalgam of what went before (which didn't work) and what I've gleaned from MS documentation.
DC1 has DNS servers setup as itself and DC2 (primary and secondary)DC2 has DNS servers setup as DC1 and itself (primary and secondary) Do you have an account set up as proxy for the DHCP server to register users?
Discard A and PTR records when lease is deleted Dynamically update for DHCP clients that do not request updates Our domain's zone is configured as an AD-Integrated zone with replication to all DNS servers in the forest.If you find that you can not resolve IP’s back to a name on your network check your DNS REVERSE LOOKUP ZONE.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.I also read that a service account should be configured to carry out the zone updates - which I have now done. Our domain's zone is configured as an AD-Integrated zone with replication to all DNS servers in the forest.Dynamic updates are set to Secure Only, and Aging is 2 hours no-refresh, 6 hours refresh intervals.