Dhcp not updating dns records
From there, the client continues communicating with the primary DNS server that accepted the A record update.
Please see For a static client, the client will communicate directly with the authoritative DNS server to update its PTR record.
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.
Statically-set clients (static clients) that perform dynamic updates will send updates for both its A record (forward lookup record) and its PTR record (reverse lookup record) to the authoritative DNS server.
And if I do a manual ipconfig/registerdns it works, every time. Pictures attached of DHCP and DNS Dynamic updates setup - this should be correct, I've always done it like this.
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.
However, in many cases when the DHCP and DNS configurations have inconsistencies, the LDNS may direct the DHCP client to a place outside the local scope, resulting in leakage of private DNS updates to the global network.
The first I hear of it usually is people moaning they can't get on Youtube, since the filter doesn't know what the computer is and thus who is logged in.The following list illustrates a typical example of how a private DNS update leaks out to the global Internet. The DHCP client first sends a query to its local domain name server (LDNS) and asks for the authoritative server for the zone of its domain name (step 3).Once the DHCP client receives a response (step 4), it sends the update to the indicated server (step 5).Both DHCP clients and servers can generate DNS updates.
To turn off DNS updates on Windows 2000/XP/2003 configured with DHCP clients (refer to Figure 1): To turn off DNS updates on Window Server 2000 running DHCP Server (refer to Figure 2 below): Microsoft Windows Server 2003 automatically sends DNS updates to each of its DHCP clients.
It does appear to be the same clients again and again with the problem, but then they could just be the people trying to get on things only available on the staff web filter policy.