From a Windows command prompt, try these commands:
ping os42.com
You should get a response like this:
Pinging os42.com [216.193.194.215] with 32 bytes of data:
Reply from 216.193.194.215: bytes=32 time=157ms TTL=56
Reply from 216.193.194.215: bytes=32 time=176ms TTL=56
Reply from 216.193.194.215: bytes=32 time=176ms TTL=56
Reply from 216.193.194.215: bytes=32 time=163ms TTL=56
Ping statistics for 216.193.194.215:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 157ms, Maximum = 176ms, Average = 168ms
If you get that, then at least your DNS is working.
Other possible responses are "unknown host", or a suggestion that you got the name wrong - if that happens, the problem is your DNS - or more likely your ISP's DNS.
If you get a series of "request timed out" responses, this means your DNS is fine (otherwise your computer wouldn't be finding the IP address from the name), but there is a problem getting from your computer to your sites. Try this command:
tracert os42.com
You should get a series of numbers and host names, ending in "trace complete". If you get timeouts, or it never gets to the final destination, the problem is routing.
You'd need to take that up with your ISP.
shadow
