Reverse dns is not updating

Rated 4.75/5 based on 802 customer reviews

Can anyone tell me how to setup my DNS clients to automatically update their PTR records? I've gone through the options and everything seems to be setup correctly, there must be something I'm missing.I can do it manually by going through the "Properties" in each client, unchecking and re-checking "Update associated pointer (PTR) record" and clicking ok in the "Forward Lookup Zones" for our domain.Point your browser at https://manage.liquidweb.com/ and log in with your user ID and password.Once you are logged in click on the Domains link in the left sidebar: Then click on the DNS tab: At the bottom of the page will be a Reverse DNS header.After you create a forward lookup zone, you can use Nslookup to make sure it is properly configured and to test its integrity to host Active Directory.To start Nslookup, type the following Nslookup server set querytype=any Nslookup starts.

To fix the forward, i modified the DHCP server to always update DNS when ever it adds a new client.If the resolver cannot locate a PTR resource record for the server, you see an error message, but you are still able to perform the tests in this section.To verify the zone is responding correctly, simulate a zone transfer by typing the following: ls -d If the server is configured to restrict zone transfers, you might see an error message in Event Viewer.As far as my other settings go, in the IPv4 "Properties" under DHCP Server, I have gone to the DNS tab and made sure that "Enable DNS dynamic updates according to the settings below:", "Always dynamically update DNS A and PTR records", "Discard A and PTR records when lease is deleted", and "Dynamically update DNS A and PTR records for DHCP clients that do not request updates..." are all selected.So, does anybody have any ideas or tips or anything for me to try and implement?

Leave a Reply