Windows 2016 dns reverse lookup not updating
Make sure the reverse zone is AD-Integrated and also check the Zone Transfers tab and make sure they are allowed (generally Only to servers listed on the Name Servers tab).
The setting with some additional info: Although the policy came through just fine, even after a reboot, my client was not registering his PTR record…If your DHCP server is also a domain controller, then you are probably fine, if not, then you may want to see if the DHCP server is a member of the "Dns Update Proxy" group in AD.Then check the Security tab on the Reverse Zone and make sure that group is authorized to create all child objects (DNS records) 2) If your statically-configured hosts are not updating the reverse zone, make sure their NICs are configured to register their IP in DNS (Windows hosts are enabled for this by default).As an AD guy I was 100% confident we could get this done using GPO’s.However in the past I have seen strange behavior with the GPO settings below Administrative Templates\Network\DNS client section, and today was just the same. Below Computer Configuration DNS Client there is a setting called “Register PTR Records”.
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.