Sbs 2016 dhcp not updating dns
DHCP is on a 2012 R2 failover platform and I can see an error 1340 in the system event log when it fails to update the A record.I had a prior issue where the legacy DHCP server was set to use credentials for registering the records and I had not configured that in the new environment which was resolved in large part by updating the ACL on the record.However, the reverse DNS entries ("PTR" Records) are not.The reverse lookup zone exists, and I can add entries to it manually, but it doesn't automatically populate.I have opened up a support case with Microsoft on August 17th. So far they've enabled all auditing and logging functions and the problem happened again - it was not shown at all what deleted the DNS record even with maximum logging turned on.Tomorrow they want me to wipe out the entire DNS zone and start over from scratch :(I wonder if our problems are the same and due to some bug in 2012 R2 DNS and/or DHCP.During the troubleshooting process I wrote some scripts to ping all of our servers by name and log results.
Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange We use windows server 2003 for DNS on our network.
The forward DNS entries ("A" records) for windows machines on the domain are populated automatically.
This was not an issue when I first built the server so I'm not sure why it is now.
I have dynamic updates enabled inside DHCP with the option set to always update discard when lease is finished and dynamically update even if clients don't ask.
Search for sbs 2016 dhcp not updating dns:
The DHCP lease obviously does have both the IP and the hostname, so I'm puzzled as to why it is not updating the DNS. Jeffrey Kane: Just create a DHCP reservation for this machine and it will solve your problem.