So, this should make it so the DHCP server sends updates to the locally-configured DNS server.
In my particular case, I have 2 domain controllers which are ALSO the DNS and DHCP servers, by the way. Everything seemed like it should work, but it didn’t. So, I looked in the event viewer (System log) and saw this error: Well, what do you know?!
The DHCP client will communicate with the authoritative DNS server directly for updating its A record, but the DHCP server updates the DNS server with the client’s PTR record In some cases, a DHCP server may update a client's A record on its behalf, even if the client did not specifically request this.
This can occur with non-Windows machines that may not be able to request dynamic updates.
After the historic information has been imported from the database, we start the DNS/DHCP resolver.The end result being that if you connect a device to the network called “mainpc01”, within a few seconds of you getting an IP address, on another machine, I should be able to “ping mainpc01”On the DHCP server, at the scope level – right-click and choose Properties and click on the DNS tab: I have it set up this way because I especially wanted this for non-Windows machines.If I hook up a Raspberry Pi or brought up a Linux machine, I didn’t want to have to go chase down the new IP address.From there, the client continues communicating with the primary DNS server that is accepting the PTR record update.Please see For a DHCP client, when some particular action causes its IP address to change, such as a DHCP lease renewal, if the client supports it, it will send Client FQDN information (DHCP option 81 flags) to the DHCP server.Some customers have reported issues with Microsoft Dynamic Updates after installing virtual appliances (VAs) in their environment or installing the Umbrella Roaming Client on some machines.The most commonly reported symptom is that clients cannot resolve A or PTR records for other client machines while using the VAs or the Roaming Client for DNS resolution.Revisiting that now, It was easy enough to modify this to have WSUS report a lab machine is running on (Pro Insider Preview 1062) but i reserve the right to look silly if this does not work as expected on the full release version due in an excitingly imminent 7 days!Whilst we are on the subject of About Robert Pearman Robert Pearman is a UK based Small Business Server enthusiast.The DHCP server will use this information, along with its dynamic update configuration, to determine whether or not the DHCP server will perform the PTR record update against the authoritative DNS server on behalf of the client, or if the client will perform the PTR update against the authoritative DNS server on its own. The first step of this process still involves the client machine sending an SOA-type query to the configured DNS server.The client then receives information from the authoritative DNS server indicating which server will be processing the update.