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.Clients with dynamically-set network connections (DHCP clients) will communicate with both the authoritative DNS server and the DHCP server for updating A and PTR records.For more information about Event Viewer, see "Troubleshooting Tools" earlier in this chapter.Use the following process to verify that your DNS server is started and can answer queries.It fixed the forward DNS entries for the most part.I just manually deleted any old entries that were not uptodate. I have triple entries on the same IP and all 3 entries are wrong (they don't match the forward at all).The roaming client is lightweight software installed on Windows machines which takes in the client’s DNS queries and conditionally forwards them to Umbrella anycast resolvers.
To start Nslookup, type the following Nslookup server set querytype=any Nslookup starts.
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.
To fix the forward, i modified the DHCP server to always update DNS when ever it adds a new client.
Then I deleted all entries and restarted all the machines (of course I set the lease time to 1 day, one day prior to do the deletion).
The SOA record includes a "primary name server" field.