[VoiceOps] Cox cable "outages" and a solution

Carlos Alvarez caalvarez at gmail.com
Sat Mar 19 12:48:33 EDT 2016

I'm posting this info here because I know quite a few of us have BYOI
customers and may be affected by this.  Cox users have been reporting a lot
of outages lately in certain areas (it seems to cluster by whatever areas
Cox is making changes in).  I found that when there is a supposed outage,
the only thing that fails is DNS. You can still ping/trace/connect with an
IP address. I looked at the router's DHCP-assigned info and found that it
was seeing an IPv6 DNS as its primary, with the usual two IPv4 servers as
secondary/tertiary. Oddly, this didn't seem to happen right away, but would
happen after the router had been up for a few hours. My best guess at the
root problem is that Cox isn't properly handling IPv6 yet, even though they
are advertising it to the router.  Completely disabling IPv6 in the router
fixes it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20160319/94e3a433/attachment.html>

More information about the VoiceOps mailing list