[Outages-discussion] [outages] CableOne DNS issue?
frnkblk at iname.com
frnkblk at iname.com
Sat Mar 25 10:12:49 EDT 2017
According to CableOne's Twitter posting at 11:22 pm Central services started
restoring:
https://twitter.com/CableONEBiz/status/845491069898784771
Checking the same traceroute this morning, I now see a Phoenix hop and the
same 4.28.80.134, which suggests that the device with the IP of 4.28.80.134
is in Phoenix, which further indicates that the issue last night was some
kind of network related failure. That CableONE asked customers not to
reboot their modems suggests that access to their cable modem provision
systems was also affected, and they didn't want those systems to be slammed
as soon as connectivity was restored.
BTW, if you run a national network, don't put your authoritative name
servers behind the same network point of failure.
root at nagios:/tmp# tcptraceroute ns1.cableone.net
Selected device eth0.3, address 96.31.0.5, port 32877 for outgoing packets
Tracing the path to ns1.cableone.net (24.116.0.206) on TCP port 80 (www), 30
hops max
1 router-core-inside.mtcnet.net (96.31.0.254) 0.247 ms 0.341 ms 0.248 ms
2 sxct.sxcy.mtcnet.net (167.142.156.197) 0.273 ms 0.175 ms 0.150 ms
3 premier.sxcy-mlx.fbnt.netins.net (173.215.60.5) 1.474 ms 1.411 ms
1.411 ms
4 ins-db4-te-0-6-0-4.219.desm.netins.net (167.142.60.157) 7.770 ms 7.526
ms 7.715 ms
5 ins-dc1-po200.desm.netins.net (167.142.67.193) 8.737 ms 8.812 ms 7.557
ms
6 216.55.25.121 18.964 ms 18.983 ms 18.950 ms
7 216.156.16.186.ptr.us.xo.net (216.156.16.186) 24.925 ms 24.917 ms
24.914 ms
8 207.88.12.162.ptr.us.xo.net (207.88.12.162) 25.259 ms 26.128 ms 24.827
ms
9 207.88.13.135.ptr.us.xo.net (207.88.13.135) 25.002 ms 24.706 ms 24.686
ms
10 lag-13.ear4.Chicago2.Level3.net (4.68.127.245) 25.165 ms 25.123 ms
32.023 ms
11 * * ae-1-11.bear1.Phoenix1.Level3.net (4.69.210.157) 241.215 ms
12 4.28.80.134 67.458 ms 67.522 ms 67.398 ms
13 * * *
14 ns1.cableone.net (24.116.0.206) [closed] 67.536 ms 67.638 ms 67.521
ms
root at nagios:/tmp#
root at nagios:/tmp# tcptraceroute ns2.cableone.net
Selected device eth0.3, address 96.31.0.5, port 35762 for outgoing packets
Tracing the path to ns2.cableone.net (24.119.5.34) on TCP port 80 (www), 30
hops max
1 router-core-inside.mtcnet.net (96.31.0.254) 0.260 ms 0.208 ms 0.269 ms
2 sxct.spnc.mtcnet.net (167.142.156.194) 10.723 ms 0.196 ms 0.160 ms
3 premier.spnc-mlx.fbnt.netins.net (173.215.60.1) 4.862 ms 4.790 ms
15.821 ms
4 ins-kb1-te-12-2-3031.kmrr.netins.net (167.142.64.253) 8.509 ms 8.492 ms
8.366 ms
5 ins-kc2-et-po101.kmrr.netins.net (167.142.67.49) 8.499 ms 8.654 ms
8.679 ms
6 10ge7-3.core1.oma1.he.net (184.105.18.169) 19.224 ms 21.610 ms 25.048
ms
7 10ge12-1.core1.blp1.he.net (184.105.64.98) 20.218 ms 20.544 ms 13.523
ms
8 10ge5-9.core1.msp1.he.net (184.105.64.93) 18.398 ms 23.572 ms 23.583
ms
9 100ge13-1.core2.chi1.he.net (184.105.223.177) 30.769 ms 21.350 ms
21.371 ms
10 level3-as3356.100gigabitethernet12-1.core2.chi1.he.net (184.105.36.158)
26.706 ms 26.758 ms 26.646 ms
11 * * *
12 4.28.80.134 69.043 ms 69.020 ms 69.054 ms
13 * * *
14 ns2.cableone.net (24.119.5.34) [closed] 69.209 ms 69.115 ms 69.115 ms
root at nagios:/tmp#
Frank
From: Outages-discussion [mailto:outages-discussion-bounces at outages.org] On
Behalf Of frnkblk at iname.com
Sent: Friday, March 24, 2017 9:46 PM
To: outages-discussion at outages.org
Subject: Re: [Outages-discussion] [outages] CableOne DNS issue?
Traceroutes to the zone's A record [24.116.124.161] and ns1.cableone.net
[24.116.0.206] seem to get stuck somewhere in Chicago . 4.28.80.134 (Level 3
IP) is the last visible hop.
10 level3-as3356.100gigabitethernet12-1.core2.chi1.he.net (184.105.36.158)
31.519 ms 27.337 ms 26.194 ms
11 * * *
12 4.28.80.134 73.404 ms 68.450 ms 68.521 ms
13 * * *
10 lag-13.ear4.Chicago2.Level3.net (4.68.127.245) 25.255 ms 25.331 ms
26.475 ms
11 * * *
12 4.28.80.134 74.048 ms 67.425 ms 67.541 ms
13 * * *
Frank
From: Outages [mailto:outages-bounces at outages.org] On Behalf Of frnkblk---
via Outages
Sent: Friday, March 24, 2017 9:27 PM
To: outages at outages.org <mailto:outages at outages.org>
Subject: [outages] CableOne DNS issue?
Was just alerted that our outbound email queues have a few messages to
cableone.net queued up, because there's no MX record (even Google and
OpenDNS don't have an MX record cached).
DNSInspect (http://www.dnsinspect.com/cableone.net/10059114) is showing that
their two nameservers aren't resolving their A record.
DownDetector is reporting issues: http://downdetector.com/status/cable-one
There's also few posts on Twitter, too:
https://twitter.com/lucky_boym/status/845441576973295616
https://twitter.com/AnonySerb/status/845441954599092224
And just now posted, from CableONE:
https://twitter.com/cableONE/status/845460682560688128
Frank
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages-discussion/attachments/20170325/70be5dba/attachment-0001.html>
More information about the Outages-discussion
mailing list