Dhcp server is not updating dns records
Microsoft Dynamic DNS (DDNS) is a wonderful feature.
Combined with Active Directory (AD) it makes managing thousands of DNS records for clients and servers a breeze.
Some customers have reported issues with Microsoft Dynamic Updates after installing virtual appliances (VAs) in their environment or installing the Umbrella Roaming Client on some machines.
The most commonly reported symptom is that clients cannot resolve A or PTR records for other client machines while using the VAs or the Roaming Client for DNS resolution.
We hope this primer to troubleshooting dynamic DNS updates was able to point you in the right direction to the problem -- and a solution.
Here's a Power Shell script that lets you easily test for multiple different problem scenarios. Ensure dynamic updates are enabled on the DNS zone This is less likely to be the problem because all clients would not be working is the dynamic updates setting on the DNS zone. If set to Secure, you may begin to see more instances like the ones we'll be talking about in #4 below. Check permissions on the dns Node AD object This problem in particular was extremely hard for us to track down on one occasion.
When integrated with AD, DNS records are just AD objects.
To successfully update, the AD computer account needs to have Modify rights to its own dns Node AD object.
If the client isn't sending the update, it's not getting to the server so server troubleshooting will be useless.
Likewise, if the server is receiving the update but the record is still not getting updated then it might be a dns Node object permission problem. If you need help, this Technet article is a great resource we'd recommend for understanding the entire workflow from client to server.