Dhcp address not updating in dns
If you check your servers event viewer you will see EVENT ID 1056: The DHCP service has detected that it is running on a DC and has no credentials configured for use with Dynamic DNS registrations initiated by the DHCP service. Credentials for Dynamic DNS registrations may be configured using the command line “netsh dhcp server set dnscredentials” or via the DHCP Administrative tool.
If you want more information you may find the following useful:
Error 31, DNS Update Failed – Seen this one before? The place to look for logs is: C:\Windows\System32\dhcp, check yours out and see if you have any error 31’s.
Even if you think things are good, it doesn’t necessarily mean that everything is working as well as it should.
Next job is to run DNSCMD /info in a command prompt.
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.
If you are working with, well almost anything network intensive these days, like Antivirus or management tools, your Reverse DNS (r DNS) lookups need to be in good shape.
Before we delve any further, its time to check your DNS setup, ensure that DNSAdmin’s have full control over the entire DNS infrastructure, by going to properties and security tab on each DNS server.
Also ensure that reverse lookups are in place, and that permissions are correct on these too.
While you are on this tab, its worth setting the conflict resolution attempts to 3 or 4 which gives DHCP the opportunity to resolve any issues itself.
Once you have these credentials set, restart your DHCP server service.
Most of you won’t be running Windows 2003 anymore, but if you are, this link may be of interest: DHCP setup primarily is the place to start with this, it is often overlooked that there needs to be a username entered into DHCP to allow for these Dynamic Updates to take place.This user account only needs limited privileges, it must be a member of DNSAdmins, DNSUpdate Proxy, DHCP Users and DHCP Administrators.