DNS: 188.8.131.52 won't resolve noaa.gov sites?
jra at baylink.com
Fri Sep 2 02:41:39 UTC 2011
[ Cross-posted to NANOG and Outages; replies to outages or outages-discussion;
I would set the header, but Zimbra sucks. :-) ]
I've had my home box set to use 184.108.40.206 as its primary resolver, falling back
to the BBN anycast.
Sometime today, 220.127.116.11 appears to have stopped resolving www.noaa.gov and
; <<>> DiG 9.7.3-P3 <<>> @18.104.22.168 www.noaa.gov
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 34999
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.noaa.gov. IN A
;; Query time: 33 msec
;; SERVER: 22.214.171.124#53(126.96.36.199)
;; WHEN: Thu Sep 1 22:38:11 2011
;; MSG SIZE rcvd: 30
though it resolves Yahoo and Google and Akamai.com and everything else
I throw at it.
Digging noaa.gov at 188.8.131.52 returns what I expect.
Interesting, too, that Firefox 5.0 wouldn't DTRT, even though 184.108.40.206-3 were
the backup nameservers in my resolv.conf.
Road Runner Tampa Bay connection.
Can anyone confirm or deny? Google DNS or NOAA people here, before I go ping
NOAA staff on Twitter?
Jay R. Ashworth Baylink jra at baylink.com
Designer The Things I Think RFC 2100
Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII
St Petersburg FL USA http://photo.imageinc.us +1 727 647 1274
More information about the NANOG