Register.com DNS hosting issues
Looks like a routing issue to their DNS servers from here. traceroute to DNS020.C.REGISTER.COM (216.21.235.20), 64 hops max, 40 byte packets 1 c28.134.nauticom.net (209.195.134.28) 0.778 ms 0.894 ms 0.829 ms 2 10.11.11.9 (10.11.11.9) 1.010 ms 0.799 ms 0.829 ms 3 c246.134.nauticom.net (209.195.134.246) 1.271 ms 1.379 ms 1.350 ms 4 207.88.183.141.ptr.us.xo.net (207.88.183.141) 84.817 ms 7.764 ms 7.699 ms 5 65.106.3.185.ptr.us.xo.net (65.106.3.185) 7.606 ms 7.634 ms 7.504 ms 6 206.111.0.54.ptr.us.xo.net (206.111.0.54) 31.458 ms 28.509 ms 20.199 ms 7 Vlan424.icore1.MLN-Miami.as6453.net (66.110.9.13) 48.740 ms 36.118 ms 36.211 ms 8 ix-6-2.icore1.MLN-Miami.as6453.net (66.110.9.54) 36.328 ms 36.851 ms 36.334 ms 9 * * * 10 blackhole.prolexic.com (209.200.132.42) 36.127 ms 36.136 ms 36.298 ms 11 * Clinton Popovich Systems Engineer Consolidated Communications -----Original Message----- From: Jeffrey Negro [mailto:jnegro@billtrust.com] Sent: Friday, April 03, 2009 3:42 PM To: Dennis Burgess - LTI Cc: nanog@nanog.org Subject: RE: Register.com DNS hosting issues No ETA given to me, just the stock line of "We apologize.. blah blah... as soon as possible.. blah blah." Jeffrey Negro, Network Engineer Billtrust - Improving Your Billing, Improving Your Business www.billtrust.com <http://www.billtrust.com/> 609.235.1010 x137 jnegro@billtrust.com <mailto:jeichmann@billtrust.com> From: Dennis Burgess - LTI [mailto:dmburgess@linktechs.net] Sent: Friday, April 03, 2009 3:39 PM To: Jeffrey Negro Subject: Re: Register.com DNS hosting issues Thanks for the update :) Guess they did not get a ETA time? ----------------------------------------------------------- Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer WISPA Board Member - wispa.org <http://www.wispa.org/> Link Technologies, Inc -- Mikrotik & WISP Support Services WISPA Vendor Member Office: 314-735-0270 Website: http://www.linktechs.net <http://www.linktechs.net/> LIVE On-Line Mikrotik Training <http://www.linktechs.net/onlinetraining.asp> The information transmitted (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is intended only for the person(s) or entity/entities to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient(s) is prohibited, If you received this in error, please contact the sender and delete the material from any computer. Jeffrey Negro wrote: For anyone trying to troubleshoot any strange resolution or page loading issues, Register.com is apparently having a massive DNS hosting outage that has been going on since 2 days ago, and is still continuing. I only found out because our monitoring was complaining about one single domain on and off. After speaking with register.com support, they admitted to the ongoing issue. If anyone has reported this already on the list, I apologize in advance for the repetition. Jeffrey
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, Apr 3, 2009 at 12:52 PM, Clinton Popovich <crpopovi@nauticom.net> wrote:
Looks like a routing issue to their DNS servers from here.
traceroute to DNS020.C.REGISTER.COM (216.21.235.20), 64 hops max, 40 byte packets 1 c28.134.nauticom.net (209.195.134.28) 0.778 ms 0.894 ms 0.829 ms 2 10.11.11.9 (10.11.11.9) 1.010 ms 0.799 ms 0.829 ms 3 c246.134.nauticom.net (209.195.134.246) 1.271 ms 1.379 ms 1.350 ms 4 207.88.183.141.ptr.us.xo.net (207.88.183.141) 84.817 ms 7.764 ms 7.699 ms 5 65.106.3.185.ptr.us.xo.net (65.106.3.185) 7.606 ms 7.634 ms 7.504 ms 6 206.111.0.54.ptr.us.xo.net (206.111.0.54) 31.458 ms 28.509 ms 20.199 ms 7 Vlan424.icore1.MLN-Miami.as6453.net (66.110.9.13) 48.740 ms 36.118 ms 36.211 ms 8 ix-6-2.icore1.MLN-Miami.as6453.net (66.110.9.54) 36.328 ms 36.851 ms 36.334 ms 9 * * * 10 blackhole.prolexic.com (209.200.132.42) 36.127 ms 36.136 ms 36.298 ms 11 *
Notice: blackhole.prolexic.com blackhole =! routing issue or blackhole = routing issue Technically, both are correct. :-) - - ferg -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.5.3 (Build 5003) wj8DBQFJ1m0sq1pz9mNUZTMRAhJrAJwI437Klcg0joD8ZF1qRLhPQaC4jQCg7CoR ynmlfRuPl7oOSX8aCFzMm1A= =lJCm -----END PGP SIGNATURE----- -- "Fergie", a.k.a. Paul Ferguson Engineering Architecture for the Internet fergdawgster(at)gmail.com ferg's tech blog: http://fergdawg.blogspot.com/
Actually I found out prolexic is a DDos filter. We fixed the issue by routing their DNS traffic out another backbone, so far so good. -----Original Message----- From: Paul Ferguson [mailto:fergdawgster@gmail.com] Sent: Friday, April 03, 2009 4:11 PM To: Clinton Popovich Cc: nanog@nanog.org Subject: Re: Register.com DNS hosting issues -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, Apr 3, 2009 at 12:52 PM, Clinton Popovich <crpopovi@nauticom.net> wrote:
Looks like a routing issue to their DNS servers from here.
traceroute to DNS020.C.REGISTER.COM (216.21.235.20), 64 hops max, 40 byte packets 1 c28.134.nauticom.net (209.195.134.28) 0.778 ms 0.894 ms 0.829 ms 2 10.11.11.9 (10.11.11.9) 1.010 ms 0.799 ms 0.829 ms 3 c246.134.nauticom.net (209.195.134.246) 1.271 ms 1.379 ms 1.350 ms 4 207.88.183.141.ptr.us.xo.net (207.88.183.141) 84.817 ms 7.764 ms 7.699 ms 5 65.106.3.185.ptr.us.xo.net (65.106.3.185) 7.606 ms 7.634 ms 7.504 ms 6 206.111.0.54.ptr.us.xo.net (206.111.0.54) 31.458 ms 28.509 ms 20.199 ms 7 Vlan424.icore1.MLN-Miami.as6453.net (66.110.9.13) 48.740 ms 36.118 ms 36.211 ms 8 ix-6-2.icore1.MLN-Miami.as6453.net (66.110.9.54) 36.328 ms 36.851 ms 36.334 ms 9 * * * 10 blackhole.prolexic.com (209.200.132.42) 36.127 ms 36.136 ms 36.298 ms 11 *
Notice: blackhole.prolexic.com blackhole =! routing issue or blackhole = routing issue Technically, both are correct. :-) - - ferg -----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.5.3 (Build 5003) wj8DBQFJ1m0sq1pz9mNUZTMRAhJrAJwI437Klcg0joD8ZF1qRLhPQaC4jQCg7CoR ynmlfRuPl7oOSX8aCFzMm1A= =lJCm -----END PGP SIGNATURE----- -- "Fergie", a.k.a. Paul Ferguson Engineering Architecture for the Internet fergdawgster(at)gmail.com ferg's tech blog: http://fergdawg.blogspot.com/
Looks like we're seeing DNS queries succeeding again. Hopefully this time they'll stay up. :) -matt On Fri, Apr 3, 2009 at 1:10 PM, Paul Ferguson <fergdawgster@gmail.com> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Fri, Apr 3, 2009 at 12:52 PM, Clinton Popovich <crpopovi@nauticom.net> wrote:
Looks like a routing issue to their DNS servers from here.
traceroute to DNS020.C.REGISTER.COM (216.21.235.20), 64 hops max, 40 byte packets 1 c28.134.nauticom.net (209.195.134.28) 0.778 ms 0.894 ms 0.829 ms 2 10.11.11.9 (10.11.11.9) 1.010 ms 0.799 ms 0.829 ms 3 c246.134.nauticom.net (209.195.134.246) 1.271 ms 1.379 ms 1.350 ms 4 207.88.183.141.ptr.us.xo.net (207.88.183.141) 84.817 ms 7.764 ms 7.699 ms 5 65.106.3.185.ptr.us.xo.net (65.106.3.185) 7.606 ms 7.634 ms 7.504 ms 6 206.111.0.54.ptr.us.xo.net (206.111.0.54) 31.458 ms 28.509 ms 20.199 ms 7 Vlan424.icore1.MLN-Miami.as6453.net (66.110.9.13) 48.740 ms 36.118 ms 36.211 ms 8 ix-6-2.icore1.MLN-Miami.as6453.net (66.110.9.54) 36.328 ms 36.851 ms 36.334 ms 9 * * * 10 blackhole.prolexic.com (209.200.132.42) 36.127 ms 36.136 ms 36.298 ms 11 *
Notice:
blackhole.prolexic.com
blackhole =! routing issue or blackhole = routing issue
Technically, both are correct. :-)
- - ferg
-----BEGIN PGP SIGNATURE----- Version: PGP Desktop 9.5.3 (Build 5003)
wj8DBQFJ1m0sq1pz9mNUZTMRAhJrAJwI437Klcg0joD8ZF1qRLhPQaC4jQCg7CoR ynmlfRuPl7oOSX8aCFzMm1A= =lJCm -----END PGP SIGNATURE-----
-- "Fergie", a.k.a. Paul Ferguson Engineering Architecture for the Internet fergdawgster(at)gmail.com ferg's tech blog: http://fergdawg.blogspot.com/
participants (3)
-
Clinton Popovich -
Matt Baldwin -
Paul Ferguson