Dhcp not updating dns server 2016
Thirdly, and this is the secret sauce to the perfect storm, the client has to behave in an anomalous manner as described here: In this specific case, the client was a Lexmark T650 series network printer.
When the device was power cycled, it would send two BOOTP Request messages.
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.
Here is a screenshot of BOOTP being disabled on the scope.
Note: “This is a modified configuration supported for DHCP servers running Windows Server 2008 and DHCP clients.
In this mode, the DHCP server always performs updates of the client’s FQDN, leased IP address information, and both its host (A) and pointer (PTR) resource records, regardless of whether the client has requested to perform its own updates.” “With secure dynamic update, only the computers and users you specify in an ACL can create or modify dns Node objects within the zone.
I found that my DNS servers had scavenging set for 3 days and my dhcp scope was set to 1 day leases.
I changed the scavenging and then made sure that I selected to scavenge for stale resource records.