Silly PUCK/Outages question
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
Not resolving on Comcast in Chicago either. -brandon On 9/24/08, Laurence F. Sheldon, Jr. <LarrySheldon@cox.net> wrote:
Tuc, stuck on puck wrote:
I hate to use NANOG for outages... But can anyone else get to
puck.nether.net or the outages.org list?
outages.org doesn't even resolve here (cox in Omaha).
On Wed, Sep 24, 2008 at 2:48 PM, Laurence F. Sheldon, Jr. <LarrySheldon@cox.net> wrote:
Tuc, stuck on puck wrote:
I hate to use NANOG for outages... But can anyone else get to puck.nether.net or the outages.org list?
outages.org doesn't even resolve here (cox in Omaha). $ dig NS outages.org @tld2.ultradns.net ;; QUESTION SECTION: ;outages.org. IN NS
;; AUTHORITY SECTION: outages.org. 86400 IN NS puck.nether.net. outages.org. 86400 IN NS anyns.pch.net. $ dig NS outages.org @204.61.216.4 ;; QUESTION SECTION: ;outages.org. IN NS ;; AUTHORITY SECTION: org. 172800 IN NS D0.ORG.AFILIAS-NST.org. org. 172800 IN NS TLD1.ULTRADNS.NET. org. 172800 IN NS C0.ORG.AFILIAS-NST.INFO. org. 172800 IN NS TLD2.ULTRADNS.NET. org. 172800 IN NS B0.ORG.AFILIAS-NST.org. org. 172800 IN NS A0.ORG.AFILIAS-NST.INFO. incorrect NS record setup maybe?? -chris
On Wed, 24 Sep 2008, Christopher Morrow wrote: > ;; AUTHORITY SECTION: > outages.org. 86400 IN NS puck.nether.net. > outages.org. 86400 IN NS anyns.pch.net. > > incorrect NS record setup maybe?? That too. We're moving the records we have over to anyns, which should pick them up within the hour. -Bill
Perhaps you should report it to outages? ;-) On Sep 24, 2008, at 11:55 AM, Christopher Morrow wrote:
On Wed, Sep 24, 2008 at 2:48 PM, Laurence F. Sheldon, Jr. <LarrySheldon@cox.net> wrote:
Tuc, stuck on puck wrote:
I hate to use NANOG for outages... But can anyone else get to puck.nether.net or the outages.org list?
outages.org doesn't even resolve here (cox in Omaha). $ dig NS outages.org @tld2.ultradns.net ;; QUESTION SECTION: ;outages.org. IN NS
;; AUTHORITY SECTION: outages.org. 86400 IN NS puck.nether.net. outages.org. 86400 IN NS anyns.pch.net.
$ dig NS outages.org @204.61.216.4 ;; QUESTION SECTION: ;outages.org. IN NS
;; AUTHORITY SECTION: org. 172800 IN NS D0.ORG.AFILIAS-NST.org. org. 172800 IN NS TLD1.ULTRADNS.NET. org. 172800 IN NS C0.ORG.AFILIAS-NST.INFO. org. 172800 IN NS TLD2.ULTRADNS.NET. org. 172800 IN NS B0.ORG.AFILIAS-NST.org. org. 172800 IN NS A0.ORG.AFILIAS-NST.INFO.
incorrect NS record setup maybe??
-chris
On Wed, 24 Sep 2008, Tuc at T-B-O-H.NET wrote: > I hate to use NANOG for outages... But can anyone else get to > puck.nether.net or the outages.org list? As regards Puck, so says Jared: > INCORRECT BLOCK COUNT I=121740614 (24704 should be 24736) > CORRECT? yes > ** Phase 2 - Check Pathnames -Bill
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
http://downforeveryoneorjustme.com can't resolve it, either.
Sorry, I should have mentioned that. Tuc/TBOH
On Wed, Sep 24, 2008 at 03:15:18PM -0400, Tuc at T-B-O-H.NET wrote:
http://downforeveryoneorjustme.com can't resolve it, either.
Sorry, I should have mentioned that.
Seems to work for me now. Those that care: 1) the outages.org ns issue should hopefully be resolved 2) i've had a phantom issue that cropped up today and caused me to toy with the system some. hopefully i won't have a need to touch it again today and it can run for another 160+ days without issues. 3) sorry that this happened on a day where all the PSIRT stuff went out. I really do try to keep the host up 100% of the time, but as most people here know, there are limits to that in reality. I now return you to your regularly secheduled depeering/abuse discussion. - Jared -- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine.
Steven M. Bellovin wrote:
http://downforeveryoneorjustme.com can't resolve it, either.
That one appears to have one DNS server that is up and down, but the other two are up and I'm able to resolve and access it from here (Comcast Business connection in Florida). For outages.org, it appears that one of the two DNS servers is reporting a lame delegation (204.61.216.4), and the other isn't responding at all (204.42.254.5). The two sites are not using the same DNS servers, so likely unrelated issues. -Justin Scott
participants (10)
-
Bill Woodcock -
Brandon Galbraith -
Brian Raaen -
Christopher Morrow -
Jared Mauch -
Justin Scott -
Laurence F. Sheldon, Jr. -
Rodney Joffe -
Steven M. Bellovin -
Tuc at T-B-O-H.NET