If you're waiting on DNS scavenging, there's no fast way to do it.
Just let it ride until you're seeing id 2501 events in the DNS Server event logs.
I'm afraid that you're going to have to approach this from the client end.
Changing the timeouts is only going to help clients the next time they check in, which is usually after half the existing lease time, or sometimes during boot.
You can approach this by manually forcing the clients to check in.
You might be able to do this by tweaking some group policy settings, or by running a script to bulk "ipconfig /registerdns" on a bunch of clients.
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.P1.el5 (as well as chroot) dhcp-3.0.5-13.el5 I have 2 identical physical hosts connected alone on a switch, no connections to any other networks.One of which is the nameserver for a test domain on a 10.10.0.0 network.Two domain controllers also have a DHCP and DNS role.Each DHCP server has the 'DNS dynamic updates registration credentials' setting populated with a user account which is a member of the 'Dns Update Proxy' group, and (although I've seen arguments for and against) I've added the servers themselves to the 'Dns Update Proxy' group. Please visit this page to clear all LQ-related cookies.