View Single Post
Old 2014-09-09, 19:01   #670
Madpoo
Serpentine Vermin Jar
 
Madpoo's Avatar
 
Jul 2014

63158 Posts
Default

Quote:
Originally Posted by chalsall View Post
A URL (or URI) is not (in and of itself) a domain (although it includes one) and thus can't be converted by the DNS system into an IP (which is what the ping targets).
Yeah, what you said.

Pinging works on the FQDN (fully qualified domain name), not a URI with the http, ftp, whatever.

I was a little hesitant at first to even allow ICMP through to the new server when I was setting up the firewall, but in the end I did because it is a pretty good troubleshooting tool to make sure you can "see" the server at all.

ICMP isn't as bad as it used to be when there were all kinds of ways you could attack it like the ping of death, etc.

Anyway, besides pinging, you can also do a plain "nslookup www.mersenne.org" to check that it's looking up the right address. It's not foolproof though because nslookup will always do a fresh query of DNS, but by doing a ping it will use any cached IP it has on your OS.

And then you can do more fun troubleshooting like (on Windows):
nslookup -type=any www.mersenne.org

And then you see that "www" is really just a cname to the @ record. And doing the same -type=any for just plain mersenne.org gets you the real deal, an A record to the IP address.

Your DNS client does the cname->A-record lookups automagically, but hey, maybe I just blew some people's minds with that info.
Madpoo is offline   Reply With Quote