Windows 2016 reverse dns not updating
This is because the client will not update itself due to the current record in DNS is beyond the lease period.
This happens even though DHCP registered the record.
This is because DHCP doesn’t own the record, the client does, even though DHCP registered it.
The way to get around this is you can configure DHCP’s Option 081 to update the record for all client, no matter if the client asks or not.
Also, it will allevaite another issue – If DHCP is on a DC, it will not overwrite the original host record for a machine getting a new lease with an IP previoulsy belonging to another host. Quoted from the following link: “Name squatting occurs when a non-Windows-based computer registers in Domain Name System (DNS) with a name that is already registered to a computer running a Windows® operating system.To configure DHCP Option 081, you must look at the DHCP server properties, under the DNS Tab in DHCP properties. If you have Windows 2008 R2 or Windows 2012 R2, in addition to configuring the DNS tab to force registration, you still must configure credentials and add the server to the Dns Update Proxy group.Despite it being a DHCP Option, it’s not found in a DHCP server, scope or class option. After configuring the above provedure, the credentials and Dns Update Proxy group configuratuion will not update current or delete duplicate records. If DHCP is on a Windows 2008 R2 DC, to protect the DC when using the Dns Update Proxy group, you must secure the group by running: dnscmd /config /Open Acl On Proxy Updates 0 Using “DHCP Name Protection.” will register A and PTR record on behalf of a client, and will prevent a workstation (non-Windows) Name Squatting, meaning using a name that another machine (non-Windows or Windows) client that DHCP already registered , from registering it’s name.This applies to Windows 2000 Professional and all newer operating systems.For domain controllers, due to the importance of keeping up to date and accurate SRV and other records, the Netlogon service will attempt to update these records every 60 minutes.
If there is a problem with PTRs getting updated even after configuring credentials, please see this article: DHCP server processes expired PTR resource records in Windows Server 2003 . The use of Name Protection in the Windows Server® 2008 R2 operating system prevents name squatting by non-Windows-based computers.