Microsoft dhcp is not updating dns
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.
This user account only needs limited privileges, it must be a member of DNSAdmins, DNSUpdate Proxy, DHCP Users and DHCP Administrators.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.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.Next job is to run DNSCMD /info in a command prompt.
The bit you are interested in here is the Listen Addresses, the image above is from a site where I have corrected this issue already.
On an uncorrected system you would see the following: Listen Addresses: If you have more than one server, the IP addresses are separated by a space.
Once completed, run DNSCMD again and check that your server IP’s now appear in the Listen Addresses section.
Job done, Dynamic DNS updates should now be functioning correctly, and there should be no more Error 31’s in your DHCP logs.
***UPDATE*** Even after all this, if you are still receiving error 31, and your DHCP lives on the domain controller, it is also necessary to put the Domain Controllers Computer Accounts in the DNSUpdate Proxy Group too in order to get truly successful updating!
Hello, We have started to have lookup problems in out network.