Dns server reverse lookup not updating
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. Credentials for Dynamic DNS registrations may be configured using the command line “netsh dhcp server set dnscredentials” or via the DHCP Administrative tool.Open up the log tab and make sure the top two entries are all zones running and running.If they are not set to that, you did something wrong. Point the DNS server setting of a device or PC to your new DNS server and use ping to try out the A, CNAME and MX records we created. This means if you perform the same lookup within a few minutes of each other the DNS does not actually do the lookup it looks in its cache first, it can do this quicker then performing the lookup. Any queries that cannot be resolved need to be forwarded to another DNS server.If this is you first install rename the file settings.example to settings.Edit the settings file with the details for your system.
Download and untar the files into a convenient place.
This is done by some applications to verify the “other” server is who they say they are. Create an NS record for the names server of our domain.
Then create the PTR type records for mailserver, myblog and mythtvserver, along with the others you may need.
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: This is required if you have DHCP installed on a Domain Controller.