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.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.
I found that my DNS servers had scavenging set for 3 days and my dhcp scope was set to 1 day leases.
I changed the scavenging and then made sure that I selected to scavenge for stale resource records.
What this means in practice is the following: This means the DHCP server computer account will own certain records in DNS, such as the PTR records and even some A records for older hosts.
(However, it's unlikely that you would have many NT 4.0 hosts in your environment.) This can cause the following two problems: For this reason, DHCP servers could be added to a group called Dns Update Proxy.
Job done, Dynamic DNS updates should now be functioning correctly, and there should be no more Error 31’s in your DHCP logs.