On Thu, Nov 21, 2013 at 06:17:24PM -0500,
David Dagon <da...@sudo.sh> wrote
a message of 31 lines which said:
> Trying from various locations, I can't seem to reach these
> authorities:
By the way, this is not the full list. The real one is larger (returned
here by f.gtld-servers.net):
;; ADDITIONAL SECTION:
ns3.msft.net. 172800 IN A 213.199.180.53
ns3.msft.net. 172800 IN AAAA 2a01:111:2020::1:1
ns1.msft.net. 172800 IN AAAA 2a01:111:2005::1:1
ns1.msft.net. 172800 IN A 65.55.37.62
ns5.msft.net. 172800 IN AAAA 2a01:111:200f:1::1:1
ns5.msft.net. 172800 IN A 65.55.226.140
ns2.msft.net. 172800 IN AAAA 2a01:111:2006:6::1:1
ns2.msft.net. 172800 IN A 64.4.59.173
ns4.msft.net. 172800 IN A 207.46.75.254
ns4.msft.net. 172800 IN AAAA 2404:f800:2003::1:1
And the difference is important because, during the outage, the IPv6
servers responded fine:
% check-soa -i microsoft.com
ns1.msft.net.
2a01:111:2005::1:1: OK: 2013112102 (146 ms)
65.55.37.62: ERROR: Timeout
ns2.msft.net.
2a01:111:2006:6::1:1: OK: 2013112102 (97 ms)
64.4.59.173: ERROR: Timeout
ns3.msft.net.
2a01:111:2020::1:1: OK: 2013112102 (15 ms)
213.199.180.53: ERROR: Timeout
ns4.msft.net.
2404:f800:2003::1:1: OK: 2013112102 (287 ms)
207.46.75.254: ERROR: Timeout
ns5.msft.net.
2a01:111:200f:1::1:1: OK: 2013112102 (100 ms)
65.55.226.140: ERROR: Timeout
(2300 UTC during the outage)
So, people with a modern DNS resolver (one using IPv6 to talk to
upstream) had no problems.
Now, if someone from Microsoft can explain why IPv4 was down on all
these sites and not IPv6, I'm all ears...
_______________________________________________
dns-operations mailing list
dns-operations@lists.dns-oarc.net
https://lists.dns-oarc.net/mailman/listinfo/dns-operations
dns-jobs mailing list
https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
