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.
Note: “This is a modified configuration supported for DHCP servers running Windows Server 2008 and DHCP clients.This issue affects Windows Server 2016 installed with the Server with Desktop Experience option.If you install any applications which add shortcut items inside a folder on the Start menu, the shortcuts will not work until you log out and log back in again. Some systems may exhibit reduced storage performance when running a new install of Windows Server 2016 versus Windows Server 2012 R2.If you attempt to run Microsoft Exchange 2016 CU3 on Windows Server 2016, you will experience errors in the IIS host process W3 You should postpone deployment of Exchange 2016 CU3 on Windows Server 2016 until a supported fix is available.If you are running a version of Windows 10 older than the Anniversary Update, and are using Hyper-V and virtual machines with an enabled virtual Trusted Platform Module (including shielded virtual machines), and then install the version of RSAT provided for Windows Server 2016, attempts to start those virtual machines will fail.In this mode, the DHCP server always performs updates of the client’s FQDN, leased IP address information, and both its host (A) and pointer (PTR) resource records, regardless of whether the client has requested to perform its own updates.” “With secure dynamic update, only the computers and users you specify in an ACL can create or modify dns Node objects within the zone.By default, the ACL gives Create permission to all members of the Authenticated User group, the group of all authenticated computers and users in an Active Directory forest.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.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.With the default settings, a duplicate A record gets registered by DHCP with the client’s new IP.This is because the client will not update itself due to the current record in DNS is beyond the lease period.