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).
It fixed the forward DNS entries for the most part.
In Windows 2008 and above, there is an option in the DHCP scope to set up the DHCP server to automatically update the authoritative DNS servers with the host (A) and PTR) records of the DHCP clients.
You must enable DNS dynamic updates and choose the option for "Always dynamically update DNS A and PTR records, and to Discard A and PTR records when the lease is deleted.
Is there a way to update my records correctly and still keep the DHCP on my Sonicwall?
Windows 2008 Sonicwall 2040- DHCP server Scavaging is turned on Multi-site VPN using sonicwalls All sonicwalls use the DNS server as main Any help on this would be appreciated!
The problem is this: when the network adapter is configured for DHCP and the DHCP server doesn't register DNS records on behalf of its clients (because it can't, or because it's not configured to do so), then in the TCP/IP settings of the network interface: As much as it may appear strange, this is the only solution to ensure Windows will register both the A and the PTR records for a DHCP network connection; otherwise, it will only register the A record.
I ran into the same issue years ago the following group policy settings are how I resolved it.
But checking the boxes for "Register this connection's address in DNS" and "Use this connection's DNS suffix in DNS registration" makes it work.
I don't have a convenient test environment to try it...
If there are missing entries, you likely have your DHCP missing one of two settings: This is required if you have DHCP installed on a Domain Controller.
It is an issue on Server 2000, 2003, 2008, 2008R2, Server 2012, Server 2012 R2 and will likely be an issue in the newer builds.
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).