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.
Dont have a router there, only a 3750 tied in via a fiber link.
I have been looking at the Cisco docs for getting this to work but nothing yet.
Also, I have a number of stale records in the reverse lookup zone that I really can't explain.
The PTR is really annoying but not critical but the fact that we often end up with duplicates or incorrect A records is much more problematic.
The way we solve this is by manually deleting the offending records and issue "ipconfig /registerdns" on the client.
DHCP is setup to always update dynamic A and PTR records in DNS servers.Any ideas why it would be a problem all of a sudden.I've a network which is mainly Windows: Windows 2008 server (with DNS/DHCP as well as AD), and various mainly Windows machines (servers, XP, 7).Would appreciate any pointers on getting this to work.Hi, I have some Windows 7/Vista clients that aren't updating their DHCP address with Dynamic DNS. I have one machine that still has its DNS from May and is now in a completely different ip range and vlan. Under the properties of the scope I have - Always dynamically update DNS A and PTR records checked and Discard A and PTR records when lease expires. I have tried refereshing DHCP credentials for Domain Admin in advanced tab but no luck.We have not installed any windows updates for last few months and no change has been made recently on server roles.First is the "simple" way to do it (which just means fewer moving parts); having the ubuntu boxes send DNS update commands to the DNS server.is the means for this, it's in the dnsutils package. 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.