It might be easier to drop your scope lease time really low, then delete all the dynamic DNS records and let them get re-created.

If you're waiting on DNS scavenging, there's no fast way to do it.

In case your DHCP server is a standalone Windows Server 2012 server, you can use the local administrator account credentials to log on while making the above configurations in the DHCP server.

Here is how you can enable the DNS integration with the Windows Server 2012 DHCP server: Once done, click OK to save the changes that you have made.

Those records have an ACL on them to stop registered records from being hijacked by other hosts.

When DHCP is used to allocate IP addresses, the default configuration is shown below—which tells the DHCP server to register records in DNS on behalf of clients only if requested to do so by the client or if the client is unable to dynamically register (e.g., Windows NT 4.0).

Just let it ride until you're seeing id 2501 events in the DNS Server event logs.

(However, it's unlikely that you would have many NT 4.0 hosts in your environment.) This can cause the following two problems: For this reason, DHCP servers could be added to a group called Dns Update Proxy.You, as a DHCP administrator, might want to enable DNS integration in order to automatically update the DNS records dynamically with the DHCP client computers’ information whenever the DHCP server assigns the IP address and other settings to them.Since the DHCP server always assigns the dynamic IP addresses to the client computers which may change from time to time, and the DNS maintains the records of the information about the host names and their corresponding IP addresses, there must be some technology with the help of which the DNS server records can automatically get updated with the latest IP addresses that the DHCP server has assigned to the DHCP clients.With the help of DNS integration with the DHCP, you can simplify this task and can remarkably reduce the administrative overhead.Just like other DHCP administration configurations, even this one requires that you should use the Enterprise Admin or Domain Admin account credentials to make the changes. If the clients happen to pick up their IP from the server then all is fine but if they get it from the router's DHCP then the DNS record on the server does not get updated even though dynamic updates is set to 'nonsecure and secure'. This is on the same subnet but a different IP range.