Ptr records not updating server 2016
The record appeared in the reverse DNS zone as expected. I do think you can use the GPO if you want to fine-tune the registration behavior as it contains 3 options. I haven’t found a way to do this by GPO, I might have missed it though.I thought GPO preferences would be the easiest way, but this setting is located below HKEY_LOCAL_MACHINE\SYSTEM\Current Control Set\services\Tcpip\Parameters\Interfaces\Register Adapter Name and the GUID is different for each system… The following command can be executed in order the check the required option: netsh interface ipv4 set dnsservers name="Local Area Connection" source=dhcp register=both In our environment we deploy all workstations using SCCM so the above is definitely a reasonable solution.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.
I set this back to 7 days, in an attempt to give DNS a chance to 'catch up' before the addresses potentially changed again, but we're still getting incorrect DNS entries. Our settings are now an amalgam of what went before (which didn't work) and what I've gleaned from MS documentation.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…