Ok I did a little investigation here. Not sure if it means anything or not, but I did want to point out what I noticed.
I got thinking if maybe something is not right as far as the difference between the following two url's
URL #1: http://www.msn.com
URL #2: msn.com
I did both a nslookup and a ping to both. Its interesting that both return a different IP back. Ping's don't resolve, but I don't think that means a whole lot, as I can get to the page just fine.
nslookup msn.com
Server: pfsense.localdomain
Address: 192.168.1.1
Non-authoritative answer:
Name: msn.com
Address: 65.55.206.228
nslookup www.msn.com
Server: pfsense.localdomain
Address: 192.168.1.1
Non-authoritative answer:
Name: us.co1.cb3.glbdns.microsoft.com
Address: 131.253.34.194
Aliases: www.msn.com
ping msn.com
Pinging msn.com [65.55.206.228] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 65.55.206.228:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
ping www.msn.com
Pinging us.co1.cb3.glbdns.microsoft.com [131.253.34.194] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 131.253.34.194:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
So, take that for what its worth.
What prompted me to investigate this was the thread about some people not being able to get to
navy.mil
but they could get to
http://www.navy.mil
due to the fact there are no A records for the first. You can get there to the first one, if your browser appends the www. in front of it first.
The tread that I'm talking about is below
»
[DNS] Can Comcast customers get to navy.mil?Again, not sure if this is the same issue or not, but I did want to point this out in case it could help shed some light on the issues that people are having.
--Brian