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.
The DHCP server will use this information, along with its dynamic update configuration, to determine whether or not the DHCP server will perform the PTR record update against the authoritative DNS server on behalf of the client, or if the client will perform the PTR update against the authoritative DNS server on its own. The first step of this process still involves the client machine sending an SOA-type query to the configured DNS server.
The client then receives information from the authoritative DNS server indicating which server will be processing the update.
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.
Check the DNS client service of the new computer The DNS client service is the service that does the actual update.
Clients with dynamically-set network connections (DHCP clients) will communicate with both the authoritative DNS server and the DHCP server for updating A and PTR 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.
We hope this primer to troubleshooting dynamic DNS updates was able to point you in the right direction to the problem -- and a solution.
When a problem occurs start from the client and work your way back.