This behavior occurs if the Client_Computer_Name$ account already exists for the DNS record.The DHCP server does not have permissions to the records in DNS.Did you find something wrong with the information on this page?

When the DNS client is configured to use a static IP address, the DNS client registers both host (A) resource records and pointer (PTR) resource records on the DNS server.

Then, the DNS client adds the Client_Computer_Name$ account together with Full Control permissions for the DNS record.

Finally, the DHCP server adds the DHCP_Computer_Name$ account together with Full Control permissions for the DNS record.

In this case, the DHCP server registers both the host (A) resource record and the pointer (PTR) resource record.

Microsoft Windows operating systems support a feature that dynamically updates the mappings of domain names to associated IP addresses assigned to hosts by DHCP servers.

This automatic updating, called Dynamic DNS Updates service, reduces the administrative overhead associated with manually administering DNS records of network hosts.

It is important to understand how clients update their DNS records dynamically to prevent issues where the process fails due to poor management of your DNS zones and records.

Many DNS administrators find that the Dynamic DNS update process, and aging/scavenging processes may be difficult to understand and manage correctly.

Hi, In short, I'm hoping for some reason behind DDNS not updating PTR records when a host changes IPs.

It suggests in DDNS and infoblox documentation that PTR records should by dynamically updated.

Then, the DHCP server adds the DHCP_Computer_Name$ account together with Full Control permissions for the DNS record.