Hi, Anyone else having problems resolving nist.gov?
From Comcast and Cyber Wurx.
dig +trace nist.gov ; <<>> DiG 9.7.3 <<>> +trace nist.gov ;; global options: +cmd . 9977 IN NS g.root-servers.net. . 9977 IN NS d.root-servers.net. . 9977 IN NS l.root-servers.net. . 9977 IN NS i.root-servers.net. . 9977 IN NS h.root-servers.net. . 9977 IN NS a.root-servers.net. . 9977 IN NS c.root-servers.net. . 9977 IN NS m.root-servers.net. . 9977 IN NS f.root-servers.net. . 9977 IN NS j.root-servers.net. . 9977 IN NS k.root-servers.net. . 9977 IN NS b.root-servers.net. . 9977 IN NS e.root-servers.net. ;; Received 228 bytes from 4.2.2.2#53(4.2.2.2) in 1 ms gov. 172800 IN NS a.gov-servers.net. gov. 172800 IN NS b.gov-servers.net. ;; Received 136 bytes from 192.203.230.10#53(e.root-servers.net) in 1 ms nist.gov. 86400 IN NS dns-x.boulder.nist.gov. nist.gov. 86400 IN NS gdnsea.nist.gov. ;; Received 107 bytes from 209.112.123.30#53(b.gov-servers.net) in 15 ms ;; connection timed out; no servers could be reached
Same for me on TWC Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Sun, Jul 1, 2012 at 12:01 PM, Bugs <bugs@debmi.com> wrote:
Hi,
Anyone else having problems resolving nist.gov?
From Comcast and Cyber Wurx.
dig +trace nist.gov
; <<>> DiG 9.7.3 <<>> +trace nist.gov ;; global options: +cmd . 9977 IN NS g.root-servers.net. . 9977 IN NS d.root-servers.net. . 9977 IN NS l.root-servers.net. . 9977 IN NS i.root-servers.net. . 9977 IN NS h.root-servers.net. . 9977 IN NS a.root-servers.net. . 9977 IN NS c.root-servers.net. . 9977 IN NS m.root-servers.net. . 9977 IN NS f.root-servers.net. . 9977 IN NS j.root-servers.net. . 9977 IN NS k.root-servers.net. . 9977 IN NS b.root-servers.net. . 9977 IN NS e.root-servers.net. ;; Received 228 bytes from 4.2.2.2#53(4.2.2.2) in 1 ms
gov. 172800 IN NS a.gov-servers.net. gov. 172800 IN NS b.gov-servers.net. ;; Received 136 bytes from 192.203.230.10#53(e.root-servers.net) in 1 ms
nist.gov. 86400 IN NS dns-x.boulder.nist.gov. nist.gov. 86400 IN NS gdnsea.nist.gov. ;; Received 107 bytes from 209.112.123.30#53(b.gov-servers.net) in 15 ms
;; connection timed out; no servers could be reached
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Same here. National Institue of Spotty Telecommunications? ;) Cheers, Dave Hart
On Sun, Jul 01, 2012 at 12:01:58PM -0400, Bugs <bugs@debmi.com> wrote a message of 111 lines which said:
Anyone else having problems resolving nist.gov?
Same problem from two different places (North America and Europe). Only two name servers, both dead. % dig @132.163.4.9 NS nist.gov ; <<>> DiG 9.7.3 <<>> @132.163.4.9 NS nist.gov ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
;; connection timed out; no servers could be reached
yes, same here frok uk hso and uk vmhosts dig @132.163.4.9 NS nist.gov ; <<>> DiG 9.7.3-P3 <<>> @132.163.4.9 NS nist.gov ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached ./dig @132.163.4.9 NS nist.gov ; <<>> DiG 9.6.1-P3 <<>> @132.163.4.9 NS nist.gov ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached Colin
I checked this morning and they're now working. Frank -----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Colin Johnston Sent: Sunday, July 01, 2012 11:27 AM To: Stephane Bortzmeyer Cc: outages@outages.org Subject: Re: [outages] NIST.gov
;; connection timed out; no servers could be reached
yes, same here frok uk hso and uk vmhosts dig @132.163.4.9 NS nist.gov ; <<>> DiG 9.7.3-P3 <<>> @132.163.4.9 NS nist.gov ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached ./dig @132.163.4.9 NS nist.gov ; <<>> DiG 9.6.1-P3 <<>> @132.163.4.9 NS nist.gov ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached Colin _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
FYI a lot of power outages in DC/MD/VA area last week and I believe they are continuing. Bill Church wmchurch@gmail.com +1 727-483-4360 (mobile) On Jul 2, 2012, at 9:17 AM, Frank Bulk wrote:
I checked this morning and they're now working.
Frank
-----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Colin Johnston Sent: Sunday, July 01, 2012 11:27 AM To: Stephane Bortzmeyer Cc: outages@outages.org Subject: Re: [outages] NIST.gov
;; connection timed out; no servers could be reached
yes, same here frok uk hso and uk vmhosts
dig @132.163.4.9 NS nist.gov
; <<>> DiG 9.7.3-P3 <<>> @132.163.4.9 NS nist.gov ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
./dig @132.163.4.9 NS nist.gov
; <<>> DiG 9.6.1-P3 <<>> @132.163.4.9 NS nist.gov ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
Colin
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
All the utility outage maps out that way are still showing *numerous* outages. I suspect there will be people running on generator out there at least into late this week. I noticed on Saturday that we lost sync with tick.usno.navy.mil (and also tock...) for some 19(ish) hours starting late Friday night. -Bill FYI a lot of power outages in DC/MD/VA area last week and I believe they are continuing. Bill Church wmchurch@gmail.com +1 727-483-4360 (mobile)
Yes. This was my dig of Google's public DNS servers: ; <<>> DiG 9.9.1-RedHat-9.9.1-1.fc17 <<>> @8.8.8.8 nist.gov ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 48583 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;nist.gov. IN A ;; Query time: 2015 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Sun Jul 1 16:17:45 2012 ;; MSG SIZE rcvd: 37 On Sun, Jul 1, 2012 at 12:01 PM, Bugs <bugs@debmi.com> wrote:
Hi,
Anyone else having problems resolving nist.gov?
From Comcast and Cyber Wurx.
dig +trace nist.gov
; <<>> DiG 9.7.3 <<>> +trace nist.gov ;; global options: +cmd . 9977 IN NS g.root-servers.net. . 9977 IN NS d.root-servers.net. . 9977 IN NS l.root-servers.net. . 9977 IN NS i.root-servers.net. . 9977 IN NS h.root-servers.net. . 9977 IN NS a.root-servers.net. . 9977 IN NS c.root-servers.net. . 9977 IN NS m.root-servers.net. . 9977 IN NS f.root-servers.net. . 9977 IN NS j.root-servers.net. . 9977 IN NS k.root-servers.net. . 9977 IN NS b.root-servers.net. . 9977 IN NS e.root-servers.net. ;; Received 228 bytes from 4.2.2.2#53(4.2.2.2) in 1 ms
gov. 172800 IN NS a.gov-servers.net. gov. 172800 IN NS b.gov-servers.net. ;; Received 136 bytes from 192.203.230.10#53(e.root-servers.net) in 1 ms
nist.gov. 86400 IN NS dns-x.boulder.nist.gov. nist.gov. 86400 IN NS gdnsea.nist.gov. ;; Received 107 bytes from 209.112.123.30#53(b.gov-servers.net) in 15 ms
;; connection timed out; no servers could be reached
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Be sure to note the long delay (45 sec) too. Use of -4 (force IPv4) also has no bearing, just as a data point. $ dig +trace nist.gov ; <<>> DiG 9.8.3-P1 <<>> +trace nist.gov ;; global options: +cmd . 72795 IN NS c.root-servers.net. . 72795 IN NS b.root-servers.net. . 72795 IN NS j.root-servers.net. . 72795 IN NS i.root-servers.net. . 72795 IN NS e.root-servers.net. . 72795 IN NS f.root-servers.net. . 72795 IN NS d.root-servers.net. . 72795 IN NS l.root-servers.net. . 72795 IN NS g.root-servers.net. . 72795 IN NS k.root-servers.net. . 72795 IN NS a.root-servers.net. . 72795 IN NS h.root-servers.net. . 72795 IN NS m.root-servers.net. ;; Received 512 bytes from 192.168.1.1#53(192.168.1.1) in 428 ms gov. 172800 IN NS b.gov-servers.net. gov. 172800 IN NS a.gov-servers.net. ;; Received 133 bytes from 2001:500:2d::d#53(2001:500:2d::d) in 245 ms nist.gov. 86400 IN NS dns-x.boulder.nist.gov. nist.gov. 86400 IN NS gdnsea.nist.gov. ;; Received 107 bytes from 209.112.123.30#53(209.112.123.30) in 45218 ms ;; connection timed out; no servers could be reached -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | On Sun, Jul 01, 2012 at 12:01:58PM -0400, Bugs wrote:
Hi,
Anyone else having problems resolving nist.gov?
From Comcast and Cyber Wurx.
dig +trace nist.gov
; <<>> DiG 9.7.3 <<>> +trace nist.gov ;; global options: +cmd . 9977 IN NS g.root-servers.net. . 9977 IN NS d.root-servers.net. . 9977 IN NS l.root-servers.net. . 9977 IN NS i.root-servers.net. . 9977 IN NS h.root-servers.net. . 9977 IN NS a.root-servers.net. . 9977 IN NS c.root-servers.net. . 9977 IN NS m.root-servers.net. . 9977 IN NS f.root-servers.net. . 9977 IN NS j.root-servers.net. . 9977 IN NS k.root-servers.net. . 9977 IN NS b.root-servers.net. . 9977 IN NS e.root-servers.net. ;; Received 228 bytes from 4.2.2.2#53(4.2.2.2) in 1 ms
gov. 172800 IN NS a.gov-servers.net. gov. 172800 IN NS b.gov-servers.net. ;; Received 136 bytes from 192.203.230.10#53(e.root-servers.net) in 1 ms
nist.gov. 86400 IN NS dns-x.boulder.nist.gov. nist.gov. 86400 IN NS gdnsea.nist.gov. ;; Received 107 bytes from 209.112.123.30#53(b.gov-servers.net) in 15 ms
;; connection timed out; no servers could be reached
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
participants (10)
-
Bill Church -
Bill Wichers -
Bugs -
Colin Johnston -
Dave Hart -
Frank Bulk -
Jeremy Chadwick -
Jonathan Nalley -
Josh Luthman -
Stephane Bortzmeyer