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

Notice:

blackhole.prolexic.com

blackhole =! routing issue or blackhole = routing issue

Technically, both are correct. :slight_smile:

- - ferg

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.

Looks like we're seeing DNS queries succeeding again. Hopefully this
time they'll stay up. :slight_smile:

-matt