Re: Silly PUCK/Outages question

[Brian Raaen <braaen () zcorum com>]

As I'm unable to resolve the DNS name, I can't reach them either.  Their 
secondary server in the whois is not giving correct info either


braaen@brian-debian:~$ dig @204.42.254.5 PUCK.NETHER.NET

; <<>> DiG 9.5.0-P2 <<>> @204.42.254.5 PUCK.NETHER.NET
; (1 server found)
;; global options:  printcmd
;; connection timed out; no servers could be reached
braaen@brian-debian:~$ 
braaen@brian-debian:~$ 
braaen@brian-debian:~$ 
braaen@brian-debian:~$ 
braaen@brian-debian:~$ 
braaen@brian-debian:~$ 
braaen@brian-debian:~$ 
braaen@brian-debian:~$ dig @204.61.216.4 PUCK.NETHER.NET

; <<>> DiG 9.5.0-P2 <<>> @204.61.216.4 PUCK.NETHER.NET
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58498
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 14
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;PUCK.NETHER.NET.               IN      A

;; AUTHORITY SECTION:
NET.                    172800  IN      NS      M.GTLD-SERVERS.NET.
NET.                    172800  IN      NS      A.GTLD-SERVERS.NET.
NET.                    172800  IN      NS      G.GTLD-SERVERS.NET.
NET.                    172800  IN      NS      I.GTLD-SERVERS.NET.
NET.                    172800  IN      NS      L.GTLD-SERVERS.NET.
NET.                    172800  IN      NS      B.GTLD-SERVERS.NET.
NET.                    172800  IN      NS      C.GTLD-SERVERS.NET.
NET.                    172800  IN      NS      H.GTLD-SERVERS.NET.
NET.                    172800  IN      NS      K.GTLD-SERVERS.NET.
NET.                    172800  IN      NS      E.GTLD-SERVERS.NET.
NET.                    172800  IN      NS      F.GTLD-SERVERS.NET.
NET.                    172800  IN      NS      J.GTLD-SERVERS.NET.
NET.                    172800  IN      NS      D.GTLD-SERVERS.NET.

;; ADDITIONAL SECTION:
A.GTLD-SERVERS.NET.     172800  IN      A       192.5.6.30
A.GTLD-SERVERS.NET.     172800  IN      AAAA    2001:503:a83e::2:30
B.GTLD-SERVERS.NET.     172800  IN      A       192.33.14.30
B.GTLD-SERVERS.NET.     172800  IN      AAAA    2001:503:231d::2:30
C.GTLD-SERVERS.NET.     172800  IN      A       192.26.92.30
D.GTLD-SERVERS.NET.     172800  IN      A       192.31.80.30
E.GTLD-SERVERS.NET.     172800  IN      A       192.12.94.30
F.GTLD-SERVERS.NET.     172800  IN      A       192.35.51.30
G.GTLD-SERVERS.NET.     172800  IN      A       192.42.93.30
H.GTLD-SERVERS.NET.     172800  IN      A       192.54.112.30
I.GTLD-SERVERS.NET.     172800  IN      A       192.43.172.30
J.GTLD-SERVERS.NET.     172800  IN      A       192.48.79.30
K.GTLD-SERVERS.NET.     172800  IN      A       192.52.178.30
L.GTLD-SERVERS.NET.     172800  IN      A       192.41.162.30

;; Query time: 65 msec
;; SERVER: 204.61.216.4#53(204.61.216.4)
;; WHEN: Wed Sep 24 14:58:24 2008
;; MSG SIZE  rcvd: 502




----------------------

Brian Raaen
Network Engineer
braaen () zcorum com
Tel 678-507-5000x5574


On Wednesday 24 September 2008, Tuc at T-B-O-H.NET wrote:
> Hi,
>
>       I hate to use NANOG for outages... But can anyone else get to 
> puck.nether.net or the outages.org list? A traceroute gets me into
> Chicago with NTT and then dies...(Along with high ping times between
> NY and IL for NTT)
>
>       I'm looking to see if anyone has more info about an S&D power
> event at 111 8th this morning. (And I contacted S&D and am getting
> nothing from them). 
>
>               Thanks, Tuc/TBOH