Over the weekend I was mostly dealing with severe incompetence, so if you ever need to verify that your
nameserver has been set correctly, use the following command:
dig -t NS your-site.com @your-nameserver.com
It will spit out some feedback, and you will see your website and nameserver in the output....if it is pointing to the correct
namesever, if it is not you will see a blank return! Here it is in action:
dig -t NS blog.errright.com @ns1.digitalocean.com QUESTION SECTION:;blog.errright.com.IN NS``;; ANSWER SECTION: blog.errright.com. 1800 IN NS NS2.DIGITALOCEAN.com. blog.errright.com. 1800 IN NS NS1.DIGITALOCEAN.com. blog.errright.com. 1800 IN NS NS3.DIGITALOCEAN.com. Here it is failing in action: QUESTION SECTION: blog.errright.com. IN NS
See, no answer section!
How do you know what
nameserver your site is really on?
Once again this spits out a lot of info, so to make it easier:
whois errright.com | grep -ie name\ server Name Server: NS1.DIGITALOCEAN.COM Name Server: NS2.DIGITALOCEAN.COM Name Server: NS3.DIGITALOCEAN.COM
- i : ignores case
- e : specifies the string
- \ : escapes the space
There you go, that should help you deal with a bluff merchant web admin.
At the very least, using these commands will scare him [it's always a him] into thinking you know more than he does, and you always want admin to think you know more than they do!