I am unable to get name resolution for anything within the radb.net domain from 206.191.173.0/24 in seattle, and dns[1-3].merit.net appear to be unreachable... Is anyone experiencing anything similiar? Thanks Chris Christopher Rogers - Network Engineer Marchex, Inc. - www.marchex.com w:+1.206.331.3368 m:+1.206.234.1423
Once upon a time, Christopher Rogers <crogers@marchex.com> said:
I am unable to get name resolution for anything within the radb.net domain from 206.191.173.0/24 in seattle, and dns[1-3].merit.net appear to be unreachable...
Is anyone experiencing anything similiar?
WFM: $ dig +trace whois.radb.net a ; <<>> DiG 9.5.1b2 <<>> +trace whois.radb.net a ;; global options: printcmd . 444548 IN NS k.root-servers.net. . 444548 IN NS e.root-servers.net. . 444548 IN NS f.root-servers.net. . 444548 IN NS a.root-servers.net. . 444548 IN NS g.root-servers.net. . 444548 IN NS j.root-servers.net. . 444548 IN NS l.root-servers.net. . 444548 IN NS b.root-servers.net. . 444548 IN NS d.root-servers.net. . 444548 IN NS c.root-servers.net. . 444548 IN NS h.root-servers.net. . 444548 IN NS i.root-servers.net. . 444548 IN NS m.root-servers.net. ;; Received 432 bytes from 216.180.54.2#53(216.180.54.2) in 2 ms net. 172800 IN NS a.gtld-servers.net. net. 172800 IN NS b.gtld-servers.net. net. 172800 IN NS c.gtld-servers.net. net. 172800 IN NS d.gtld-servers.net. net. 172800 IN NS e.gtld-servers.net. net. 172800 IN NS f.gtld-servers.net. net. 172800 IN NS g.gtld-servers.net. net. 172800 IN NS h.gtld-servers.net. net. 172800 IN NS i.gtld-servers.net. net. 172800 IN NS j.gtld-servers.net. net. 172800 IN NS k.gtld-servers.net. net. 172800 IN NS l.gtld-servers.net. net. 172800 IN NS m.gtld-servers.net. ;; Received 489 bytes from 193.0.14.129#53(k.root-servers.net) in 195 ms radb.net. 172800 IN NS dns1.merit.net. radb.net. 172800 IN NS dns2.merit.net. radb.net. 172800 IN NS dns3.merit.net. ;; Received 143 bytes from 192.52.178.30#53(k.gtld-servers.net) in 125 ms whois.radb.net. 1800 IN A 198.108.0.18 radb.net. 14400 IN NS dns3.merit.net. radb.net. 14400 IN NS dns1.merit.net. radb.net. 14400 IN NS dns2.merit.net. ;; Received 159 bytes from 198.108.1.43#53(dns1.merit.net) in 61 ms $ -- Chris Adams <cmadams@hiwaay.net> Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble.
Both merit.net and radb.net unreachable from RTP,NC on TWTelecom. -----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Christopher Rogers Sent: Wednesday, January 28, 2009 3:12 PM To: outages@outages.org Subject: [outages] radb down? I am unable to get name resolution for anything within the radb.net domain from 206.191.173.0/24 in seattle, and dns[1-3].merit.net appear to be unreachable... Is anyone experiencing anything similiar? Thanks Chris Christopher Rogers - Network Engineer Marchex, Inc. - www.marchex.com w:+1.206.331.3368 m:+1.206.234.1423 _______________________________________________ outages mailing list outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Appears working now... name servers were previously unreachable, then began returning nxdomain for radb.net, and now appear functional. thanks to all who replied. Chris
-----Original Message----- From: outages-bounces@outages.org [mailto:outages-bounces@outages.org] On Behalf Of Christopher Rogers Sent: Wednesday, January 28, 2009 12:12 PM To: outages@outages.org Subject: [outages] radb down?
I am unable to get name resolution for anything within the radb.net domain from 206.191.173.0/24 in seattle, and dns[1-3].merit.net appear to be unreachable...
Is anyone experiencing anything similiar?
Thanks Chris
Christopher Rogers - Network Engineer Marchex, Inc. - www.marchex.com w:+1.206.331.3368 m:+1.206.234.1423 _______________________________________________ outages mailing list outages@outages.org https://puck.nether.net/mailman/listinfo/outages
participants (3)
-
Chris Adams -
Christopher Rogers -
Dave Larter