[Outages-discussion] [outages] CableOne DNS issue?

[frnkblk at iname.com]

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
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/20170324/2b4bcfbf/attachment.html>