Dhcp not updating dns server
Issue: ========== DHCP not updating records in DNS Cause: ========== Based on below step, we can get the log of DHCP register dns record progress. Run this command in the client: netsh trace start capture=yes scenario=addressacquisition tracefile=c:.Run this command in the DHCP server: netsh trace start capture=yes tracefile=c:. Enabled Dynamically update DNS A and PTR records for DHCP clients that do not request updates If you think this article is helpful, please click on the “Recommend” button.Although really the hosts should (for the most part) be doing this on their own with out help from the DHCP server at all.Still having problems with outdated records :-/I increased the lease time from 1 day to 7 days as mentioned in the OP, but we're still getting an issue when the clients receive a new IP, they are not updating DNS with the new record and removing the old.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.If you find that you can not resolve IP’s back to a name on your network check your DNS REVERSE LOOKUP ZONE.
This might be an issue, maybe someone with more knowledge can elaborate.When I joined the company, I noted that a lot of name lookups were failing or pointing at the wrong machines.I also noted a staggering amount of old, outdated DNS records.DHCP is set as follows: Enable DNS dynamic updates - always dynamically update DNS A and PTR records.Discard A and PTR records when lease is deleted Dynamically update for DHCP clients that do not request updates As far as my understanding goes (which is clearly not far enough), DHCP should update DNS as soon as it itself updates.
I forgot to undo the commented out before pasting it here, that was from a test to see if it would work with a few things commented out.