[AZ] DNS lookup errors, stalls, lags, page not found errors agai

[AZ] DNS lookup errors, stalls, lags, page not found errors agai
Links: home · search · speed test · login · more ·

Links: Reply New Topic
Forums » US Cable Support » Cox HSI » [AZ] DNS lookup errors, stalls, lags, page not found errors agai
page: 1 · 2 · 3
jsmiddleton4 @ 28th Oct 08:48AM:
[AZ] DNS lookup errors, stalls, lags, page not found errors agai

Similar as have been reported in why the slow down in AZ and needing to reboot SB5100 router. Which I have the same model.

Symptoms exist if router in or out of system. Picked up new router just incase it was my router again, same problem with new router.

Signals seem to be fine but with the amp that was put on my modem signal strength readings are don't tell me much anymore.

Have PM'd AZ Cox tech but here we go again......

And as others have reported it is intermittent, when it happens can't get to any site, everything is just stalled. Either page not found/load error OR DNS lookup error message.
reply

CoxTech1 @ 28th Oct 09:00AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

Your modem doesn't appear to be a 5100 so it wouldn't be impacted by the older firmware issue others have reported.
reply

jsmiddleton4 @ 28th Oct 09:48AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

My bad. Its a 5101. And I didn't say I was effected by any firmware update/downgrade. Just reporting symptoms.

Had to go look it up.

If it matters this is what I have.

Software Version: SB5101N-2.7.5.0-GA-00-NOSH
Hardware Version: 1
MIB Version: II
GUI Version: 1.0

Far as I know that is what you pushed to me a couple of months ago isn't it?
reply

CoxTech1 @ 28th Oct 09:59AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

Yes, that would be the most recent for your particular model. Considering the history of problems we've had with your account it probably would be better that you messaged your local techs on this forum to investigate further.
reply

jsmiddleton4 @ 28th Oct 10:07AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

I already have messaged the local tech. We'll see but I'm not going to mess with it like the last time. My experience has taught me all too well that Cox will decide on their own if they want to really fix things or just manage symptoms. Cox will make that decision regardless of my input. And given that manage symptoms has been the m.o. in the past, I do not expect any change at this stage.

Maybe I need 2 amps?
reply

jsmiddleton4 @ 28th Oct 11:23AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

And as before its not so bad in the morning. But as the day progresses and users go up, heat not a variable now of course, page stalls and dns lookup failures start to happen.
reply

dvd536 @ 29th Oct 12:11AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

said by jsmiddleton4 :

Maybe I need 2 amps?

Maybe you need new dns servers.
try these:
4.2.2.1
4.2.2.2
--
When I gez aju zavateh na nalechoo more new yonooz tonigh molinigh - Ken Lee
reply

BillRoland @ 29th Oct 12:38AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

said by dvd536 :

said by jsmiddleton4 :

Maybe I need 2 amps?

Maybe you need new dns servers.
try these:
4.2.2.1
4.2.2.2

I've had excellent luck since switching to the above servers.
--
"Don't steal. The government hates competition."
Beyond AM. Beyond FM. XM
reply

daveinpoway @ 29th Oct 07:21AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

I personally prefer OpenDNS:

208.67.222.222
208.67.220.220
reply

jsmiddleton4 @ 29th Oct 12:20PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

I'll give both dns servers a try. Something changed though and it would be nice if Cox.... oh never mind.

Edit:

208.67.222.222
208.67.220.220

Wow, fast and snappy!
reply

madden2k5 @ 29th Oct 12:25PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

Yeah Cox's dns servers haven't been very stable in awhile. I use the 4.2.2.1 4.2.2.2 4.2.2.3 and they have run fine for me for awhile.
reply

jsmiddleton4 @ 29th Oct 12:29PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

The OpenDNS servers make a huge difference. I mean huge. So much so that it points out something isn't quite right in Dodge Marshall Dillon. In the past when I've used third party DNS servers sometimes there is an improvement, sometimes not. They don't sell themselves so to speak.

Not this time. The performance difference is stark.

Will continue to try them through the day but the last 10 minutes or so of surfing quite an improvement.
reply

CulDeSac @ 29th Oct 12:33PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

I've been using openDNS for about a year and have seen great improvements on performance.

With teenagers at home, I also use openDNS for content filtering. This free service provides an excellent way to protect my network from unwanted content.
reply

jsmiddleton4 @ 29th Oct 02:32PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

OpenDNS continues to be snappy and smokes Cox. Something that while good for me or anyone else who uses the OpenDNS server information it still leaves a finger pointing at Cox's and an indication something is not okay with theirs.
reply

dvd536 @ 29th Oct 09:39PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

said by daveinpoway :

I personally prefer OpenDNS:

208.67.222.222
208.67.220.220

great however the ones i posted are "clean dns" servers unlike opendns's servers with the redirects!
--
When I gez aju zavateh na nalechoo more new yonooz tonigh molinigh - Ken Lee
reply

daveinpoway @ 30th Oct 09:05AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

Obviously, different people have different thresholds for what annoys them, but the OpenDNS redirects have never bothered me (I have not seen them very often, anyway).

Besides, it is my understanding that they get revenue from these redirects, so that they can offer their great service to me without charge. Can't complain about that!
reply

jsmiddleton4 @ 30th Oct 09:10AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

Clean or unclean, direct or redirect, both of them out perform Cox's currently. Switched back to Cox's last night for a test. Stalls, dns lookup errors, pages not loading, etc. Back to OpenDNS, snappy, no issues, all good.

So while there will be a person or two on this forum who want to make performance issues with Cox my fault, my expectations, kinda hard to leave this one at my doorstep.

I'm sure one or two folks will try though.

Edit:

By the way I'm going to try 4.2.2.1 4.2.2.2 this morning and today.
reply

BillRoland @ 30th Oct 11:48AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

I switched off of Cox's DNS servers years ago for basically the same reason, slow lookups and timeouts. I'm hardly alone, but nobody at Cox wanted to believe it.
--
"Don't steal. The government hates competition."
Beyond AM. Beyond FM. XM
reply

dvd536 @ 31st Oct 01:41AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

said by daveinpoway :

Besides, it is my understanding that they get revenue from these redirects, so that they can offer their great service to me without charge. Can't complain about that!

But when you're trying to troubleshoot something and need clean servers. . . . .
thats my gripe.
--
When I gez aju zavateh na nalechoo more new yonooz tonigh molinigh - Ken Lee
reply

jsmiddleton4 @ 31st Oct 10:25AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

4.2.2.1 4.2.2.2

Just as snappy as OpenDNS and of course stark contrast to Cox's at this time.

Why Cox's for me took a dive I have no idea. But the performance difference is clear and Cox loses.
reply

jsmiddleton4 @ 2nd Nov 11:36AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

Found out Cox has some "opt out" dns servers. Its these addresses.

# Enter the following Preferred and Alternate DNS Server Addresses in order:

* 68.105.28.13
* 68.105.29.13

I guess you opt out of the "extra" stuff so they are suppose to be faster.

I have tried them at the suggestion of Chris/Cox Tech support. What I found is I did not have any page load/dns look up errors. But they were slower than OpenDNS or the 4.x.x.x ones. Hesitate is the best word I can use to describe using them. They seemed to hesitate. OpenDNS and 4.x.x.x. were fast and snappy and no hesitation.
reply

tubbynet @ 2nd Nov 12:09PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

my question is for all of those who are seeing connectivity issues that are resolved with dns:
what operating system and service pack are you running? i have not had any issues with cox dns (but have since switched to my own msdns server with root server lookup), but i only run various flavors of linux and xp. i do not run vista or 7 on any of my computers (too old or limited *critical* app support).
i work with several very skilled ms engineers that have explained issues on vista caused by unresponsive/slow/non-existent dns servers; even on trivial services such as telnet, ping, and tftp - all by ip.
i would like to get a general consensus so as to debate whether i should delve into the vista network stack.

q.
--
"...if I in my north room dance naked, grotesquely before my mirror waving my shirt round my head and singing softly to myself..."
reply

jsmiddleton4 @ 2nd Nov 04:29PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

64 bit Vista with sp 2.

My only ? is why issue with only Cox DNS servers given my OS stays the same? Some how Cox's became "non-existent" for whatever reason and Vista chokes? While the non-Cox ones including the opt-out ones never become "non-existent"?
reply

tubbynet @ 2nd Nov 04:31PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

said by jsmiddleton4 :

64 bit Vista with sp 2.

do you have an xp box available to test with the cox dns servers?

q.
--
"...if I in my north room dance naked, grotesquely before my mirror waving my shirt round my head and singing softly to myself..."
reply

jsmiddleton4 @ 2nd Nov 04:33PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

Not any more. Had one PC with XP and just gave it away to a family who needed a PC but couldn't afford one.

Will have Win 7 soon if Digital River can get their act together for some student qualified down loads.

I have Win 7 rc on a laptop that if Digital River can't get it going I will have to revert it back to XP with a restore. But as of today, no XP platforms available.
reply

jsmiddleton4 @ 2nd Nov 04:48PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

While I appreciate Chris from Cox's participation in this issue I find myself being puzzled by the same on-going issue with Cox support. Why is it as an end user is it up to me to prove to Cox to the nth degree that they have a problem BEFORE they will get on getting to the bottom of it and fixing it?

It is enough, at least in my feeble brain, that I can and have demonstrated there is a problem. When I use Cox's default dns servers, I have page load problems and DNS look up problems. And by golly so do other folks. When I switch off of Cox's to a third party's dns servers, I do not have problems.

So at that point and while I'm happy to help at some point, the matter is in Cox's hands. It is not up to me as an end user/customer to create a situation where Cox can not avoid dealing with this issue. When there can be no other explanations and the data supports Cox has a dns server issue then and only then Cox will do something? After I prove it beyond any reasonable doubt?

I just don't get that kind of posture towards it customers.

Cox you have a problem with your dns servers. A simple read of this thread as well as some others right here on this forum supports that observation. My experience supports that conclusion with some simple A to B comparisons.

Do I know what the problem is? No, I do not. I don't have a clue what the problem is. Am I going to continue to collect data to prove to Cox it has a problem? No, I think I'm done.

Cox will fix it quite independently, or not fix it, of me and what I may or may not discover for Cox.

So Chris, again thank you for your efforts and questions, but I'm done.

Its nap time and the 4.x.x.x servers work fine and is an acceptable work around and "acceptable work around" seems to be as good as it gets at the moment.
reply

BillRoland @ 2nd Nov 04:57PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

I've seen it on Windows 2000, XP, Server 2003, and Vista boxes. Don't know about 7, since I don't use Cox DNS servers with any 7 boxes.
--
"Don't steal. The government hates competition."
Beyond AM. Beyond FM. XM
reply

daveinpoway @ 3rd Nov 06:15AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

This morning, there was a message on the Cox HSI status page that they are having DNS problems in the San Diego area and some web sites might be unreachable. Since I use OpenDNS, I have been unaffected by this- I have able to access everything that I want.
reply

CoxTOC1 @ 3rd Nov 09:28AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

Unfortunately we don't have a routing issue category for outages and the closest thing we have is a DNS outage. It is not a DNS outage but a routing outage.
reply

khobar @ 3rd Nov 10:51AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

So what's the solution? We're all paying a lot of money to Cox, and somewhere along the line Cox made a change no doubt to "improve" our service.

I'm highly frustrated with the net being up and down the way it is now. Very strange.

Is there any way to narrow it down by polling people who DON'T have problems? What's different for them, or what's common for us?
reply

CoxTOC1 @ 3rd Nov 11:15AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

The problem currently lies off the cox network. We are actively working with the other network to try and resolve this issue.
reply

jsmiddleton4 @ 3rd Nov 11:16AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

Could this be why we are seeing the dns lookup problems though?
reply

CoxTOC1 @ 3rd Nov 11:25AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

I think that you are confusing a DNS look up problems with routing issues. Don't forget that often larger sites will have multiple locations that their site is served from. Depending on where your DNS is geographical located it will change how you actually get to the site. This will of course give a perception that it is a DNS issue when in fact it is a routing issue.
reply

joshieca @ 3rd Nov 11:34AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

I tell you what I am going to do...I am going to complain and ask for a service credit. We are playing good money each month for this service and COX needs to give some of that back!
reply

khobar @ 3rd Nov 11:55AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

I think it's high time we get an explanation as to the nature of the problem. Thus far Cox has said there is no problem on their end, that if there is a problem it is at the user's end.

Now you are acknowledging there is a problem on the Cox side but that it's not Cox's fault.

So, what exactly is going on? Please explain.
reply

CoxTOC1 @ 3rd Nov 12:05PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

said by khobar :

I think it's high time we get an explanation as to the nature of the problem. Thus far Cox has said there is no problem on their end, that if there is a problem it is at the user's end.

Now you are acknowledging there is a problem on the Cox side but that it's not Cox's fault.

So, what exactly is going on? Please explain.

Khobar at no point did I ever say that the problem exists on the users end nor did I ever acknowledging there is a problem on the Cox side but that it's not Cox's fault.

In fact I've said quite the opposite if anything.

1. It's not a DNS issue it's a routing issue.

2. The routing issue is not on the Cox network.

3. We are working with the networks and providers in question to resolve this issue.
reply

khobar @ 3rd Nov 12:31PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

You, personally, might not have said it was on the user's end, but that is EXACTLY what I've been getting from Cox when I call. And so have a lot of other people. Has Cox posted an update on their website stating they are attempting to address this issue? I just checked and the only info there pertains to difficulty logging into the webmail. Where is the notice that internet service is royally hosed and has been for some time and that Cox is currently working to correct it?

And yes, you did acknowledge there was a problem on the Cox end of things but not Cox's fault. "The problem currently lies off the cox network. We are actively working with the other network to try and resolve this issue." So you even know who the problem lies with. Interesting. Whether the routing issue is or is not on the Cox network, it is on Cox's side of the connection 'cause it sure isn't on my side.

I never said it was a DNS issue (I'm not in any position to say what the problem is or even might be), but I am currently reading other forums to see if anyone other than Cox customers are experiencing this issue. Oddly enough I've seen a number of people experiencing speed *increases*. I haven't read through all the postings so maybe others are having similar issues too.

Bottom line - I don't like being lied to. I don't like calling tech support and being told there is no problem when there really is. I don't like being brushed off and told I need to invest in new equipment to fix the problem. I don't like being told I have to disable my firewall and jump through hoops for busy work while Cox is already aware none of what they are telling me has anything to do with the issue.

I apologize for dumping on you, but this whole thing is ridiculous and my frustration level is off the charts. Make me feel better and tell me, tell us all, what the problem is exactly, and why after more than a month the issue has not been resolved. Who is "the other network" involved?
reply

CoxTOC1 @ 3rd Nov 12:46PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

The issues that I am referring to has only been ongoing for about a day. If you are experiencing a problem that has been ongoing for "months" then you are experiencing a totally different problem.

I'm sorry but I have not been authorized to give out any additional information.
reply

khobar @ 3rd Nov 12:59PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

I don't know why you'd say the problem has only existed for a day. People have been complaining to Cox about this issue for some time now, and we all get the same response: "what problem?"

As to what you did comment on, are you referring to the webmail "issue" posted yesterday?

I'm disappointed that you cannot comment further, but I do understand why.
reply

CoxTOC1 @ 3rd Nov 01:04PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

No I'm referring to the outage posted for "DNS Services" in San Diego. Because of how our network is laid out the routing issue that's posted as a DNS issue in San Diego would also be effecting AZ users.
reply

khobar @ 3rd Nov 01:34PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

Okay - thank you for the clarification.

Now, perhaps you can shed light on my and others' issue in a general sense?

Basically - what would cause the net to be fast one moment and then connection resets, resolving host, cannot connect, waiting for..., page load error, page not found error all randomly happening followed by normal operation?

What would cause such behavior to magically vanish?

I've been with Cox for a decade now. This behavior is not new - I've had it happen from time to time in the past and have been told the same thing - there is no problem. Within a very short time everything was back to normal, and it stayed that way for months, sometimes years at a time.

This time, however, is very different - the problem did not go away. I replaced my modem as instructed and the problem is the same and has been now for over a month. Sometimes the network is good for a few minutes before bogging down, and sometimes it's good for several hours or even as much as a day. I don't understand why it is so intermittent.

Can you answer me this - when I call the automated tech thing, I'm told a signal is being sent and "let's see what we get back" or something to that effect. Shortly thereafter I'm told the signal didn't come back right - words to that effect, afterwhich the modem is reset. When I eventually get to a real person they say something like "let's check the modem" and then report all is fine. My question is: what exactly is being checked and what is the difference between the automated "thing" and the live person? Is the live person simply checking the signals page in the modem?
reply

CoxTech1 @ 3rd Nov 01:38PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

Do you have a Motorola SB5100 by any chance?
reply

CoxTOC1 @ 3rd Nov 02:42PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

said by khobar :

Can you answer me this - when I call the automated tech thing, I'm told a signal is being sent and "let's see what we get back" or something to that effect. Shortly thereafter I'm told the signal didn't come back right - words to that effect, afterwhich the modem is reset. When I eventually get to a real person they say something like "let's check the modem" and then report all is fine. My question is: what exactly is being checked and what is the difference between the automated "thing" and the live person? Is the live person simply checking the signals page in the modem?

Well I am not 100% certain how the automated system looks that stuff up. But I suspect that it's using some server/process as a middle man to our poling tools. It more than likely has three "messages" that it's looking for. Good, Bad and Time Out. If it gets a answer of "Good" it will proceed to the next step. If it gets a answer of "Bad" or "Time Out" it runs the reset script. This of course is my speculation as I have no knowledge of how it works.

The difference being of course that the automated system can only deal with for lack of a better word "normal" conditions. If you get out of that it can't handle that. A real live person would be better equipped to handle things that are out of the ordinary (Like when something takes longer than expected to load).

Now to help you with your connection issue I need to understand how you are set up as well as get some basic information.

Can you gather the info in »[ALL] what to post before complaining about slow speeds...? and start a new thread so we can troubleshoot your connection?
reply

Radardan @ 4th Nov 10:47AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

jsmiddleton4 said:
I just don't get that kind of posture towards it customers.

A similar issue reflecting management's customer viewpoint is the return of an old issue on cable TV: insertion of local ads with wrong timing. It's been going on again about two months now.

It astonishes me that these timing issues can occur for months at a time, several times an hour, each and every hour on multiple channels.

I've tackled them twice before in prior years. Once I contacted the TV network and they got some executive to contact Cox about it. The last time I posted about it here and it still took several weeks to get someone on the problem.

When it occurs for weeks at a time and so frequently daily, it appears that not even Cox Media watches it's own revenue stream for quality.
reply

khobar @ 4th Nov 07:15PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

I started a new thread on this. I don't think I put it in AZ though - sorry.

»Intermittent web clogging
reply

dvd536 @ 5th Nov 12:27AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

said by Radardan :

jsmiddleton4 said:
I just don't get that kind of posture towards it customers.

Still going on here. mainly on discovery owned channels however I could care less[its an ad after all]
--
When I gez aju zavateh na nalechoo more new yonooz tonigh molinigh - Ken Lee
reply

khobar @ 5th Nov 09:50AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

No. I had an SB3100 that served me well for many years.

I replaced it with an SB6120.

Today, for the very first time since I got the new modem, I noticed that after waiting for 10 minutes for the modem to reboot it came back and showed the downstream as being "bonded". That's new.

Unfortunately, my problem remains - I'm getting very good download speeds, according to DSL Reports speedtest and speedtest.net, but crapola upload speeds of anywhere from nothing at all to 100 or so Kbps.

The only thing that seems to be consistent is the upload speed drops off the map when I'm experiencing the slowdown. I've seen upload speeds all over the place, from 100Kbps (and the overall speed seemed okay) to 4-5Mbps. I dunno what to make of that.

Speedtest.net just came back (after about 10 minutes) with an upload speed >2Mbps. For a split instant the net became unclogged - I pulled one webpage up (facebook) instantly. Went to cnn.com and it came up but much more slowly. Checked speedtest.net and my download speed is reported as 14.60Mbps, upload speed has failed to report. We'll see if it takes another 10 minutes to get through.

Weird.
reply

khobar @ 5th Nov 10:00AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

Okay, speedtest.net just came back with 0.34Mbps. But cnn.com came up quicker, so I reran the speedtest.net test. It came back quickly with the following:

download 17.67Mbps
upload 5.24Mbps

The upload speed has to be an indicator, a symptom of what's going on.
reply

jsmiddleton4 @ 5th Nov 02:29PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

Thanks for the additional IM Chris but as noted I am done investing in this dns issue. I have demonstrated with enough information that Cox has a problem. The idea that I have to go to the nth degree to convince Cox that there is a problem in hopes that after all of my trouble shooting they MAY address it is lousy customer service.

Cox apparently thinks that if customers aren't willing to go to the nth degree then Cox is off the hook.

Sad.

Your dns servers need help. Invest in fixing them or not, that is Cox's business not mine.

And as others here have pointed out when having similar issues with Cox's DNS servers, they too could not get anyone at Cox to do anything about it nor take the problem seriously.

At least Cox is consistent regarding this matter.
reply

No_Strings @ 5th Nov 03:06PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

The perennially half-empty view of things.

What if it's something more like this?

Millions of subscribers are experiencing no such symptoms, and in spite of having some smart people with decent tools it's not immediately apparent where the problem lies. Cox works with cooperative customers who are having this problem in an effort to gather additional data which may help them track down the gremlin. It's in their own interest to do so if they can and are willing since a lack of adequate information might mean a longer fix time.

Of course those customers are under no obligation to help Cox with their troubleshooting any more than a patient in a doctor's office is obligated to provide the physician with details which might aid in the diagnosis. After all, the doctor has x-rays and blood tests and education. Let him figure it out.

I guess it's all in one's perspective.
reply

AZHSISUPPRT2 @ 6th Nov 08:03AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

No_Strings is quite right. Cox is not off the hook, but unfortunately, I still have not gotten the tests from you that I asked for to be able to determine where the issue may lie.

At this time all I have received are the screen shots of the errors and I thank you for those. The screen shots that you have provided does indicate that there is an issue, however without an IP address of the DNS servers you were using when you encountered the issue is like trying to find a needle in a stack of needles.

The other descriptions of one set of servers being fast and snappy and Cox's not fast and snappy is not quantifiable information that our engineers can use to troubleshoot which is why I had asked for ping tests, traceroutes, tests with and without a firewall enabled, etc. This is essential information that our engineers need.

DNS issues are not easy to troubleshoot. I am more than willing to assist anyone having issues with DNS lookups. There are tests that I have to have the end user run in order to isolate the problem. I have to bring un-refuted information to our engineers and I know that you do not want to do any further tests and I don't blame you. It is a lot of work to track these things down.

So I ask if there is anyone else experiencing these issues that is willing to help to please PM me so I can get the information that I need to get this to our engineers.

Thanks,
--
Chris@Cox Communications Arizona
reply

jsmiddleton4 @ 11th Nov 08:27AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

Since its been several days thought I'd try Cox's DNS servers again. Same result as already reported. Stalls, lags, dns lookup errors, etc.

Back to 4.x.x.x, snappy, fast, etc.
reply

anon @ 11th Nov 07:11PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

Thankfully I found this forum.

For over 6 months I've had problems with Cox LV. First, Vonage kept dropping calls and VOIP tests showed Cox dropping packets at such a high rate that it could not be used for VOIP. This despite speed tests showing 6Mbps and higher. So I switched to an Embark hardline when Cox claimed "nothing was wrong."

Over the summer I used DSL in a rural area. Despite only 1.5Mbps, internet performance was 100% reliable.

Now back in Vegas, Cox measures 10Mbps, BUT about 25% of the time pages either never load (NYT, Apple, etc.) or never finish loading. This on both PCs and Macs.

My guess was that Cox has problems connecting to the "rest of the internet" although I can't quite explain why non-Cox speed tests work fine. (Actually the ping/litter test never finishes.)

If its the Cox DNS services -- I can add the OpenDNS servers but I can't delete the Cox DNS crap that is tried first. Any OS X users know how to delete Cox "lv.cox.net" from Network prefs? They are grayed-out. How did Cox get these stuff into my computer?
reply

Ikyuao @ 11th Nov 11:01PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

Don't erase Cox lv.cox.net from your network preference settings that may be necessary for searching the domain to spot be found to querying the DNS lists in the resolv.conf and however - I'd stored the foreign DNS proviers lists in my linux resolv.conf like that:

domain ks.cox.net
search ks.cox.net
nameserver 127.0.0.1
nameserver 4.2.2.1
nameserver 4.2.2.2
nameserver 4.2.2.3
nameserver 4.2.2.4
nameserver 4.2.2.5
nameserver 4.2.2.6
nameserver 156.154.70.1
nameserver 156.154.71.1
nameserver 208.67.222.222
nameserver 208.67.220.220
nameserver 68.105.28.11
nameserver 68.105.29.11
nameserver 68.105.28.12

my cable internet remains be more stable and having an zero problem that I ever experienced.
--
Professional Linux environmental blows microsoft windows out of the water.
reply

zipturtle @ 12th Nov 04:44AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

Most Unix platforms will only use the first 3 nameserver entries you have in your resolv.conf file.

You might want to check you Linux version to see if what you have is even valid. Check the man pages on resolv.conf(5).

Number of nameserver entires is typically defined by a value that is compiled into the binary (ie not changeable without recompiling).

Even if more than 3 were valid, you should lookup how these are used and I think you will find that having more is not a good idea. There are specified amounts of time that must elapse before the resolver moves to the next entry and having a known bad entry can make lookups very slow.

Some systems can define what the timing is, but few ever set that. I seem to recall that is is typically 5-10 seconds wait x 2 tries before the next entry. If this is the case, it would take 10-20 seconds between each name server tried. Again, refer to the man page for your machine on what that might be if it is defined.

You are much better off using 2 solid entries rather than a long list of name servers.

For my residential boxes, I use OpenDNS (I like the reports)... for my business servers I run my own bind servers with hints from root zones, using typically two designated servers for that purpose.
--
Kevin

Both Business and Residential Cox Customer.
reply

Ikyuao @ 12th Nov 07:11AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

said by zipturtle :

Even if more than 3 were valid, you should lookup how these are used and I think you will find that having more is not a good idea. There are specified amounts of time that must elapse before the resolver moves to the next entry and having a known bad entry can make lookups very slow.

More than three nameserver entries are remains be valid and it is accessible under my Linux box of resolv.conf, that doesn't making lookups very slow so you make no sense to me, DNS querying lookups which uses UDP packet traffics.

Linux is open source, it can be added more lookup querying than three DNS lookups is not a problem issues.

I use dnsmasq as lighter weight dns caching server.
--
Professional Linux environmental blows microsoft windows out of the water.
reply

round_toit @ 12th Nov 07:50PM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

I rarely post and do not care if anyone replies. I have several people on ignore and I invite anyone who does not like this post to put me on ignore.

I just changed my router to the 4.2.x.x and I am astounded. This is the fastest cox has ever been. I appreciate madden2k5 posting the dns numbers.

I have been really frustrated with cox,even after having them out many times.

To me this is amazing.
reply

zipturtle @ 13th Nov 03:59AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

Ikyuao,

May I suggest a good book.... DNS and BIND Published by O'Reilly Media. I think you would learn a lot from the information presented there. For the resolv.conf stuff we are talking about any edition of the book will do.

As for how many nameservers your resolver will accept, you could always test it... it's really simple... You can do it live right on your Debian box.

Copy your current resolv.conf file to a safe place, then create a new one with 3 bogus nameserver entries that don't point to any real name servers and then make the fourth entry a real one.

For example:
nameserver 123.123.123.123 nameserver 124.124.124.124 nameserver 125.125.125.125 nameserver 4.2.2.1

Make sure you remove all the other nameserver entries and you really don't need the domain or search lines or any of the other stuff you have in yours.

As soon as you save it, you can then use dig to lookup hostnames on your box and see what happens...

# dig -d somehostname

If you include the -d option like above, you can get some debug info showing what is actually happening as the resolver works through each of the nameserver entries and then gives you an answer .... or as I have suggested, not give you an answer as I suspect your response will be.

Then you will know for sure how many nameserver entries are actually used... Make sure to restore some real name servers when you are done so that you have working DNS on your box again.

There are a lot of good resources on the net about DNS and how it works, including some good forums where you can ask DNS admins about your configuration like on dnsstuff, though they tend to deal with authoritative nameserver like questions mostly.
--
Kevin - Both Business and Residential Cox Customer.
reply

jsmiddleton4 @ 13th Nov 09:16AM:
Re: [AZ] DNS lookup errors, stalls, lags, page not found errors

round....

The speed difference is a stark contrast isn't it? Cox does not seem to be interested in addressing it unless we go way beyond what is reasonable to prove to them they have an issue.

Given the considerable amount of difference in performance it is obvious that Cox needs to address something. Not sure what but there is something amiss with their DNS servers.
reply