How to ping my nameservers using command prompt?

  • September 11, 2017
  • 0 Comments

You can find your nameservers in your welcome e-mail. Please note that up to 24 hours are required for DNS propagation after you changed the nameservers of a domain name. The time is needed so that the nameservers all over the world can ‘understand’ about the change and start resolving your domain name from the new server. In some rare cases, the DNS propagation may take up to 72 hours. If more than 24 hours passed and your domain still points to the old server, you can do the following to verify if everything is ok with your nameservers and see if the problem is with them or the problem is with the resolvers/nameservers of your ISP.

To do that, you need to do the following in your computer: click on Start, Run, enter cmd in the command prompt and hit Enter. You will get the windows command prompt where you need to execute the following command.

nslookup yourdomain.com ns1.edohost.com

or

nslookup yourdomain.com ns2.edohost.com

Where yourdomain.com is your domain name on our server you want to check and the ns1.edohost.com and ns2.edohost.com are our primary nameservers which we provided you in our welcome e-mail and which you set for your domain name.

To find out where does your domain point to from your computer run the following command from the same command prompt:

ping yourdomain.com
In the result, if you see the IP we provided, then your domain points to our server. If it points to the IP of the old server that means there is a DNS cache on your computer or your ISP’s nameservers/resolvers. To flush the cache on your computer execute the following command:

ipconfig /flushdns
Once you flush the cache run the ping command again to see if your domain started resolving to our server’s IP.

ping yourdomain.com
If it still points to the old server’s IP you have 2 options. The first one is to wait for your ISP’s nameservers cache to expire. That may take from 2 to 12 hours or even more on a misconfigured nameserver/resolver. The second option is to call your ISP and have them clear the DNS cache for you so that your domain starts pointing to the correct IP from your computer. Do not forget to flush the cache on your computer once your ISP flushes the cache of their resolvers/nameservers.

You can use the commands above to troubleshoot DNS issues with domains and subdomains and find out the cause of the problem yourself without first contacting us.

How helpful was this article to you?