[outages] msn.com and microsoft.com
Dan White
dwhite at olp.net
Thu Nov 21 17:56:17 EST 2013
I am unable to reach msn.com, due to DNS lookup failures.
http://microsoft.com is responding very slowly within a web browser (it's A
record is cached in my nameserver).
None of the ns[1-5].msft.net nameservers are responding to queries. The
glue records for msft.net currently look to me like:
ns1.msft.net. 67622 IN A 65.55.37.62
ns5.msft.net. 67622 IN A 65.55.226.140
ns2.msft.net. 67622 IN A 64.4.59.173
ns4.msft.net. 67622 IN A 207.46.75.254
ns3.msft.net. 67622 IN A 213.199.180.53
Here is a traceroute to ns1.msft.net:
$ traceroute 65.55.37.62
traceroute to 65.55.37.62 (65.55.37.62), 30 hops max, 60 byte packets
4 olp-67-217-150-202.olp.net (67.217.150.202) 9.998 ms 9.998 ms 10.057
ms
5 12.249.72.53 (12.249.72.53) 14.930 ms 14.931 ms 14.925 ms
6 cr81.tlsok.ip.att.net (12.123.16.238) 7.774 ms 9.796 ms 9.385 ms
7 cr1.dlstx.ip.att.net (12.122.1.201) 7.951 ms 7.954 ms 7.952 ms
8 gar23.dlstx.ip.att.net (12.122.85.69) 6.479 ms 6.486 ms 6.591 ms
9 * * *
10 207.46.47.36 (207.46.47.36) 17.687 ms * 17.918 ms
11 207.46.40.202 (207.46.40.202) 58.563 ms 58.570 ms 58.541 ms
12 207.46.46.93 (207.46.46.93) 57.360 ms 57.358 ms 57.498 ms
13 207.46.43.209 (207.46.43.209) 58.007 ms * *
14 * 10.22.12.2 (10.22.12.2) 57.363 ms 57.366 ms
15 * * *
16 * * *
17 * * *
This issue may be limited to the Dallas area. Can anyone else confirm
access?
Thank You,
--
Dan White
More information about the Outages
mailing list