If you are working with, well almost anything network intensive these days, like Antivirus or management tools, your Reverse DNS (rDNS) lookups need to be in good shape. If you find that you can not resolve IP’s back to a name on your network check your DNS REVERSE LOOKUP ZONE. If there are missing entries, you likely have your DHCP missing one of two settings:
SET DHCP TO AUTOMATICALLY CREATE DNS ENTRIES
- Launch DHCP
- Right click on your SCOPE and select PROPERTIES
- Click the DNS tab
- Make sure that the following settings are on
- ENABLE DNS DYNAMIC UPDATES
- ALWAYS DYNAMICALLY UPDATE DNS A AND PTR RECORDS
- DISCARD A AND PTR RECORDS WHEN LEASE IS DELETED
- DYNAMICALLY IPDATE DNSA a AND PTR RECORDS FOR DHCP CLEINTS THAT DO NOT REQUEST UPDATES
- ENABLE DNS DYNAMIC UPDATES
SET CREDENTIALS TO ALLOW DHCP SET TO DYNAMICALLY UPDATED DNS ENTRIES
- Using Active Directory Users and Computers create a standard domain user and set the password to DOES NOT EXPIRE.
- Launch DHCP
- Right click on IPv4 and select PROPERTIES
- Select the ADVANCED tab
- Click the CREDENTIALS button
- Enter the user information you created in step one
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 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. This is not a recommended security configuration. 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:
http://technet.microsoft.com/en-us/library/c0e87732-985c-4c9c-83b4-70c679cad748.aspx
http://support.microsoft.com/kb/282001
5 Comments
HgSysIt · January 24, 2017 at 8:10 am
thanks!
Faisal Khan · May 8, 2016 at 10:03 am
Thank You for sharing the information, i have faced this issue and tried in the forums but could not find a solution for that.
all solutions was very complicated .
Bookmarked and Thumbs up!
Will Smith · March 8, 2015 at 4:04 pm
I was having the issue of DHCP not updating DNS records. I searched everywhere, asked in forums and got a lot of complicated, convoluted answers. Thanks for the CONCISE, CORRECT answer, Cheers!
Jack · February 27, 2015 at 7:42 am
I had a similar issue with permissions on Windows Server 2012 R2 I think I solved them with your fix. I also followed the tutorial I found on Youtube https://www.youtube.com/watch?v=Tukvch2Qtuc so far so good! Thank You
ME · February 13, 2015 at 9:55 am
If the supplied credentials belong to an object (such as a computer) that is a member of the DnsUpdateProxy security group, the next object to register the same name record in DNS will become the record owner.
If you specified the credentials (user name, domain, and password) that the DHCP server uses when registering DHCP client computers in DNS, these credentials are not backed up with either synchronous or asynchronous backup. After a DHCP database is restored, new credentials must be configured.