US Cable Support > Cox HSI > AZ- DNS Servers Down?

reply to CoxTech1

Re: AZ- DNS Servers Down?

Yes, since you have D-Link you wouldn't need to do the fix either. As those that need to do the fix do so and/or are removed from the network the DNS issues will get better for everybody else.

gotcha. very interesting problem.

reply to swingtrader
As of 11am local time here, things seem to be back to normal now.

Edit- Spoke too soon, mostly back to normal, a few stragglers still slow loading, or missing images/layout/etc..

reply to swingtrader
8.8.8.8 and 8.8.4.4 if those go down it's because god decides no more internet.

reply to irontoes
We think we have a grasp on the root cause of the issue at this time. Getting those customers fixed so it doesn't happen again however is something we're still trying to work out.

reply to CoxTech1
I switched to that firmware over a year ago on my netgear because I was having dns issues personally. This problem, for everyone, just started today and there are not anymore version 1 or 2's of that netgear router being sold for over a year so why would this cause this now all of a sudden?

Also, I'm sure there are hundreds or thousands of people that have that router and I'm sure only a handful come to this forum so how would they know to upload that firmware anytime soon so it fixes it for the rest of us?

reply to swingtrader
I was down with Cisco modem in Peoria/Glendale. Put Google's DNS servers in my Asus router and the problem went away.

I've used non-COX DNS servers before but had returned to the default ones for Cox so I knew what to do.

Hardly seems like an installed equipment issue on the user side.

The issue gets quite complicated but there appears to be an issue with a particular firmware generating lots of traffic.

reply to jsmiddleton4
Here's the official word FYI

»ww2.cox.com/residential/arizona/···00000000

reply to swingtrader
Both Twitter and Amazon sites have crashed today. That butterfly is sure flapping its wings.

reply to CoxTech1
Ok, so can you explain why I can no longer get the 3 IP address's through my SB6120 since this issue happened? I have called the COX support and they cannot tell me why I no longer get the 3 IP's that I am suppose to get. I can only get one device to work now since this has happened.

reply to swingtrader
It's good to see it's not just me. Seems the issue is still ongoing with various old and new customer equipment from what I've found so far. I was wondering if anyone has any suggestions for alternate ipv6 DNS server settings. I see that Google has open servers for ipv6 but I'm looking to stay away from going through anything of Googles.

reply to swingtrader
I'm sorry but that explanation doesn't line up with our experience.

I went from not having any access to having no issues by just changing my DNS Server addresses in my router.

If the explanation is accurate then how is it my changing dns servers fixes the symptom?

reply to swingtrader
Is this issue still ongoing? I'm using Google's Public DNS and thing have been great. Especially enjoying the new speed upgrades here in Phoenix.

reply to CoxTech1

reply to swingtrader
So a bad firmware on some else's router is putting extra traffic "out there" on Cox's part of the web that is messing up the rest of our dns server addresses?

I don't know whether to be insulted or feel sorry for folks who might actually believe that explanation.

reply to swingtrader
Up and down and up and down and up and down all night in NE Phoenix.

Now I'm on the phone with "support" who denies seeing a modem on my account even though I'm seeing a tiny little sliver of "up" at the moment. Doesn't matter which DNS I use if the modem is losing sync with the network and not coming back online. It's a Cisco DPQ3212 EMTA... have temporarily taken a phone line to do SOMETHING about reducing the gigantic bill for TV and internet.

I expect I will lose service completely during the call, the serial number of the device has been requested. "It's odd, you say you have internet but I have no modem listed on your account." This will not end well...

And it went downhill from there. While I was on hold I lost connectivity. "There is no internet modem on your account. I can fill out a form with your serial number or you can take the modem to a cox store." No dial tone on the phone line anymore either. Awesome support, leaving me worse off than I started!

As for my intermittent connectivity? "The modem was maybe picking that up via wifi."

It's magic.

She can fill out the form, whatever. Since the call my modem has now gone into a cycle of try to synch, then give up completely, try to synch... whatever. It's outta here on Saturday. Bye, COX.

I'll definitely be heading to the cox store on Saturday - with the EMTA, 3 cable cards and 3 tuning adapters. $160 per month for this garbage service and it ends here. Life will go on without cable.

CenturyLink has had a brand-new DSLAM a few hundred feet from my front door for the last year. Just ordered 40/20 service. And I know I'm trading one set of problems for perhaps a different set of problems.

reply to swingtrader
I think the complication comes from the fact that its was a two fault problem. This is just my opinion of what happened based on reading this and a couple other threads.

First a new firmware was released for the WNDR3700v1. Since they update firmware automatically by default, the firmware bug in that release effected all routers of that type simultaneously.

This caused two problems. A, each WNDR3700v1 was unable to query DNS, causing many with that router to be unable to get online. B, that same bug caused each router to have issues with the automatic time update features of those routers to send useless "trash" traffic to the DNS servers they got through DHCP. This caused those DNS servers to slow down or stop functioning all together. Its possible other DNS servers are set to drop any incoming "trash" traffic of that type.

Not everyone with a WNDR3700v1 was effected by problem A. Some disabled the firmware auto update. But everyone in the area using the standard DNS was effected, no matter what router. To stop the outbound traffic, disabling the time feature and rebooting the router worked. Changing the DNS if you had the WNDR3700v1 is a temp fix, but I feel that's just pushing the problem onto another DNS. But it was the main fix for people with other routers but still effected.

Probably what Cox eventually did was block that traffic until they could set the DNS servers to ignore it. Then hopefully each WNDR3700v1 will automatically patch itself when Netgear pushes the now beta firmware as a public release.

reply to CoxTech1