How to correct reverse DNS issues

Most of the time people think of DNS as being the service that helps us to resolve a name to an IP address and that is certainly true, as without this service, the Internet as we know it could not exist today, or at least it would be very “un-user friendly.”  The other side to DNS however, that it is equally important in its own right, is reverse DNS.  Reverse DNS allows one to take a known IP address and translate that into a useful “friendly” name.  This can cause major headaches when it isn’t working properly as the incorrect host name will be used if reverse DNS is stale.

How do you troubleshoot this on your local workstation?  Well, there is a very useful command that can accomplish leaps and bounds with both forward and reverse DNS look ups.  By using the ipconfig command with a command line switch, we can effectively clear out our stale DNS cache that exists on our machine.  If you have an IP address that you KNOW for sure is supposed to link to a specific name and it doesn’t, you can flush your DNS cache to see if this resolves the issue.



By issuing the above command, ipconfig /flushdns we are telling our computer to effectively flush out any DNS entries it may have and then get a fresh copy of what your DNS server thinks the hosts should resolve to.  This way, if something has changed on the server side, you will be sure to get the latest host names from the server instead of from your local machine, which could be stale.

To test and make sure things are resolving correctly, we can issue the trusty ping command with a special switch to test our reverse lookup.



The ping -a %ip% command is the command we can use to test our reverse DNS resolver.  You should receive the correct host name back if your DNS is pulling the correct settings.

System Administrators

On a DNS server, sometimes what can also happen is that reverse DNS entries can become stale and incorrect entries or many entries for one IP address can sometimes pile up.  In Microsoft’s DNS server, you can check your reverse DNS entries to verify you only have one host name for the particular IP address in question.  If not, you have stale entries that may be causing problems with clients who are resolving IP addresses to hostnames.

Subscribe to VirtualizationHowto via Email 🔔

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Brandon Lee

Brandon Lee is the Senior Writer, Engineer and owner at and has over two decades of experience in Information Technology. Having worked for numerous Fortune 500 companies as well as in various industries, Brandon has extensive experience in various IT segments and is a strong advocate for open source technologies. Brandon holds many industry certifications, loves the outdoors and spending time with family.

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.