Dhcp server not updating dns records; microsoft.support = microsoft.support
I don't have a convenient test environment to try it...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.When a new client gets an IP address, DHCP doesn't update DNS with the record. The DHCP and DNS are on the same box (which is also the primary DC).I have checked the event viewer logs for the DHCP and DNS server but nothing is present?
On a semi related note: I know this has been a touchy subject some places I have looked. For each DC, what should their local DNS settings be?