Hello, DNS is not my strong suit, so hopefully this is simple to more practiced hands.
I have a DC that provides internal DNS for our company, but DHCP is handled by the firewalls in each branch.
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.
And are they configured to send DNS updates in their network adapter settings?
Is there any reason you wouldn't just have the router provide DHCP at all times?
This association, or mapping, of an IP address to a domain name requires that a change in either the address or the name necessitates an update of the information in DNS.The DHCP protocol does not automatically update DNS in the event that the DHCP server changes the IP address of a client.To facilitate this interaction, servers running Windows Server® 2008 and DHCP and clients running DHCP can register with DNS, allowing cooperation between the two.My DNS entries are not updating with the information from DHCP (time stamps, new IPs, etc.).I assume there's a link missing between the two that needs to be established?