Internet Service Providers forum

Resolved Question

About DNS server error...

by cardmast3r / May 24, 2014 7:13 AM PDT

I've been investigating lag spikes for weeks now on my internet, and I can't seem to fix this error (DNS server not responding). I can connect to the internet just fine, but lag spikes really kill my gaming experience. I've gone through multiple gateways, comcast laid a new line and replaced an old splitter, but still they can't fix it. They say my signal is just fine and want me to upgrade my speed. This happens on multiple devices (computers, Xbox, etc.). When I changed to a public DNS, the error goes away, but the lag is still there. My connection is fine for minutes at a time, but gets spikes that eventually DC some of my games and Xbox Live, which is rather annoying. It doesn't seem to happen at any specific time of day either. This happens around the clock. Does anyone have any ideas? I'm thinking about trying to change my ISP, but Comcast has a monopoly around here.

cardmast3r has chosen the best answer to their question. View answer
Discussion is locked
You are posting a reply to: About DNS server error...
The posting of advertisements, profanity, or personal attacks is prohibited. Please refer to our CNET Forums policies for details. All submitted content is subject to our Terms of Use.
Track this discussion and email me when there are updates

If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.

You are reporting the following post: About DNS server error...
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.

All Answers

Best Answer chosen by cardmast3r

Collapse -
Fixed
by cardmast3r / June 8, 2014 3:22 AM PDT

After contacting the president of Comcast, he sent a bunch of techs to find the problem. Turns out it was interference from a home down the street. Apparently it could not be detected by normal means. The 4th tech that came out to my house actually knew a thing or 2, and when he checked the ping test results he knew something was wrong. Internet has been fantastic ever since. I appreciate all of your input!

Collapse -
Answer
open your router program
by James Denison / May 24, 2014 1:49 PM PDT

set your DNS to something other than what your ISP gave you. A popular one is from google 8.8.8.8 and 8.8.4.4

Collapse -
Answer
DNS
by Adventi / May 25, 2014 2:46 AM PDT

Good Afternoon,

If you are still receiving lag with either OpenDNS or Google's DNS then you will need to supply more information, a traceroute via the CMD prompt would allow us to see the routing of the network to see if you are gaining lag..

However, when you have changed the DNS are you sure your not currently receiving slow speeds as well?

Please perform a speed-test and run this via CMD:
tracert www.google.com

This will show your routing path to google.com and will show any latency spikes on the way or anything that seems to be causing the issue. That is if the speedtests are not slow.

From what it sounds like, comcast DNS is probably not the greatest (never used it so my opinion is invalid) however with most ISP DNS it will no way be as good as OpenDNS or Google's DNS. Therefore, you may get drops etc. However it sounds when you change it to a public IP address you are in general receiving slow speeds anyway.

Look forward to your response.

Thanks,

Aaron

Collapse -
Re
by cardmast3r / May 25, 2014 6:21 AM PDT
In reply to: DNS

Here are the results of the traceroute:
Tracing route to www.google.com [208.117.244.250]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.0.0.1
2 52 ms 24 ms 30 ms 71.58.172.1
3 10 ms 11 ms 11 ms te-0-0-0-2-sur01.montville.pa.pitt.comcast.net [
68.85.43.1]
4 2366 ms 11 ms 11 ms 69.139.194.65
5 18 ms 31 ms 16 ms te-8-8-ar01.pittsburgh.pa.pitt.comcast.net [69.1
39.195.173]
6 29 ms 28 ms 27 ms he-4-15-0-0-cr01.newyork.ny.ibone.comcast.net [6
8.86.94.189]
7 27 ms 27 ms 31 ms he-4-9-0-0-cr01.ashburn.va.ibone.comcast.net [68
.86.87.61]
8 35 ms 27 ms 28 ms be-16-pe03.350ecermak.il.ibone.comcast.net [68.8
6.82.218]
9 27 ms 27 ms 27 ms as36040-8-c.ashburn.va.ibone.comcast.net [66.208
.233.178]
10 26 ms 28 ms 26 ms cache.google.com [208.117.244.250]

Trace complete.

Seems to be a huge spike in there. I confirmed via CMD that I'm using the google DNS (8.8.8.8 and 8.8.4.4), with no change.

Collapse -
Where is the spike?
by R. Proffitt Forum moderator / May 25, 2014 6:56 AM PDT
In reply to: Re

I see each hop is well under 100ms. What's sad is that it took that many hops from you to the server. That can increase the chance of lag by a lot.

But here we are with a lead question about DNS, DNS failure, some great advice about changing DNS and then a traceroute to what is not the game server.

Try sharing what game server this is and a trace to it.

My son plays some online games and has figured out that he will have to change servers if the lag time gets too high.
Bob

Collapse -
Here?
by cardmast3r / May 25, 2014 7:15 AM PDT
In reply to: Where is the spike?

4 2366 ms 11 ms 11 ms 69.139.194.65

Is this not a problem?

Collapse -
Got it.
by R. Proffitt Forum moderator / May 25, 2014 8:49 AM PDT
In reply to: Here?

te-0-12-0-3-ar03.lowerpaxton.pa.pitt.comcast.net so it's one of comast's routers so not under your control.

Nice finding but for years folk have had little luck in getting the big carriers to fix bottlenecks like that.
Bob

Collapse -
Well...
by cardmast3r / May 25, 2014 10:18 AM PDT
In reply to: Got it.

I emailed the CEO of Comcast about this. Have yet to get a response since yesterday evening, but it is memorial day weekend so hopefully I'll get something next week. The one tech from Comcast I talked to yesterday said pretty much the same thing. It's probably a complicated server issue that Comcast won't pay to fix until it gets out of hand. Anything else I should do?

Collapse -
If it's a game, try other game servers.
by R. Proffitt Forum moderator / May 25, 2014 11:25 AM PDT
In reply to: Well...

One of the downsides of all the cord cutting and the rise of video over internet is that bottlenecks will happen. You can see Comcast has named the cities by the routers so what you found is there is a bottleneck at that point.
Bob

Collapse -
I expect this response...
by Adventi / May 25, 2014 5:13 PM PDT
In reply to: Well...

Hi guys,

I can tell you know I can expect this response...MS reacts differently to ICMP through the core network, therefore you may notice MS spikes while going through them...

If it receives to the end with a low MS then as they advise, it doesn't actually matter...Unfortunately, I am not 100% sure on this information, however this was advised by my Network specialists...The people who build the network infrastructure at my place..Did you run a speed-test mate?

Can you confirm if this is just a game server that is having problems? I've spent nights where I was so bored that I have helped people with game servers, and have actually found faults in there network before...So don't give up Happy Also, there is some MS tricks that can reduce your latency through editing the registry...However, I am not going to give advise on how to do this as its very serious if you mess it up and destroy your PC.

As well, can you please do the following CMD as well. As I want to see if its giving the lag spikes then.

Please perform the following CMD:
ping www.google.co.uk -t

Then after about five-ten minutes just press ctrl+C at the same time and it will cancel this CMD.

If this supplies latency and/or intermittent packet drops, then you will have some hard evidence to back your case up....If you need any further assistance with pulling some weight against them and using technical jargon to blow them out of the water and to force you to get some assistance...Just ask for some advise, I know how to word things in the networking industry and I also know what is required to show solid evidence of network faults...Considering I work in the industry.

Thanks,

Aaron

Collapse -
Also in a private conversation
by Adventi / May 25, 2014 5:16 PM PDT

Also, to add-on, I am more than happy to have a debate with anyone from Comcast through Email for fun....

Meaning, if you need me to get involved and do the required checks I ask for, I will get action done for you.

Private message me if you can, just been using this site recently so I am not sure, ill have a look

Collapse -
Ping test
by cardmast3r / May 26, 2014 6:37 AM PDT

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\*******>ping www.google.com -t

Pinging www.google.com [208.117.244.183] with 32 bytes of data:
Reply from 208.117.244.183: bytes=32 time=28ms TTL=56
Reply from 208.117.244.183: bytes=32 time=28ms TTL=56
Reply from 208.117.244.183: bytes=32 time=21ms TTL=56
Reply from 208.117.244.183: bytes=32 time=33ms TTL=56
Reply from 208.117.244.183: bytes=32 time=23ms TTL=56
Reply from 208.117.244.183: bytes=32 time=28ms TTL=56
Request timed out.
Reply from 208.117.244.183: bytes=32 time=22ms TTL=56
Reply from 208.117.244.183: bytes=32 time=2698ms TTL=56
Reply from 208.117.244.183: bytes=32 time=24ms TTL=56
Reply from 208.117.244.183: bytes=32 time=27ms TTL=56
Reply from 208.117.244.183: bytes=32 time=2673ms TTL=56
Reply from 208.117.244.183: bytes=32 time=34ms TTL=56
Reply from 208.117.244.183: bytes=32 time=25ms TTL=56
Reply from 208.117.244.183: bytes=32 time=27ms TTL=56
Request timed out.
Reply from 208.117.244.183: bytes=32 time=3990ms TTL=56
Reply from 208.117.244.183: bytes=32 time=21ms TTL=56
Reply from 208.117.244.183: bytes=32 time=32ms TTL=56
Reply from 208.117.244.183: bytes=32 time=2510ms TTL=56
Reply from 208.117.244.183: bytes=32 time=24ms TTL=56
Reply from 208.117.244.183: bytes=32 time=2477ms TTL=56
Reply from 208.117.244.183: bytes=32 time=22ms TTL=56
Reply from 208.117.244.183: bytes=32 time=2756ms TTL=56
Reply from 208.117.244.183: bytes=32 time=23ms TTL=56
Reply from 208.117.244.183: bytes=32 time=23ms TTL=56
Reply from 208.117.244.183: bytes=32 time=22ms TTL=56
Request timed out.
Reply from 208.117.244.183: bytes=32 time=2194ms TTL=56
Reply from 208.117.244.183: bytes=32 time=25ms TTL=56
Reply from 208.117.244.183: bytes=32 time=22ms TTL=56
Reply from 208.117.244.183: bytes=32 time=30ms TTL=56
Reply from 208.117.244.183: bytes=32 time=24ms TTL=56
Reply from 208.117.244.183: bytes=32 time=2394ms TTL=56
Reply from 208.117.244.183: bytes=32 time=22ms TTL=56
Reply from 208.117.244.183: bytes=32 time=2618ms TTL=56
Reply from 208.117.244.183: bytes=32 time=24ms TTL=56
Reply from 208.117.244.183: bytes=32 time=19ms TTL=56
Reply from 208.117.244.183: bytes=32 time=22ms TTL=56
Request timed out.
Reply from 208.117.244.183: bytes=32 time=29ms TTL=56
Reply from 208.117.244.183: bytes=32 time=24ms TTL=56
Reply from 208.117.244.183: bytes=32 time=24ms TTL=56
Reply from 208.117.244.183: bytes=32 time=22ms TTL=56
Reply from 208.117.244.183: bytes=32 time=32ms TTL=56
Reply from 208.117.244.183: bytes=32 time=23ms TTL=56
Reply from 208.117.244.183: bytes=32 time=19ms TTL=56
Reply from 208.117.244.183: bytes=32 time=27ms TTL=56
Reply from 208.117.244.183: bytes=32 time=2839ms TTL=56
Reply from 208.117.244.183: bytes=32 time=21ms TTL=56
Reply from 208.117.244.183: bytes=32 time=22ms TTL=56
Reply from 208.117.244.183: bytes=32 time=22ms TTL=56
Request timed out.
Reply from 208.117.244.183: bytes=32 time=1577ms TTL=56
Reply from 208.117.244.183: bytes=32 time=22ms TTL=56
Reply from 208.117.244.183: bytes=32 time=21ms TTL=56
Reply from 208.117.244.183: bytes=32 time=2686ms TTL=56
Reply from 208.117.244.183: bytes=32 time=24ms TTL=56
Reply from 208.117.244.183: bytes=32 time=27ms TTL=56
Reply from 208.117.244.183: bytes=32 time=24ms TTL=56
Reply from 208.117.244.183: bytes=32 time=22ms TTL=56
Request timed out.
Reply from 208.117.244.183: bytes=32 time=1579ms TTL=56
Reply from 208.117.244.183: bytes=32 time=22ms TTL=56
Request timed out.
Reply from 208.117.244.183: bytes=32 time=1497ms TTL=56
Reply from 208.117.244.183: bytes=32 time=22ms TTL=56
Reply from 208.117.244.183: bytes=32 time=3263ms TTL=56
Reply from 208.117.244.183: bytes=32 time=24ms TTL=56
Reply from 208.117.244.183: bytes=32 time=23ms TTL=56
Reply from 208.117.244.183: bytes=32 time=33ms TTL=56

Ping statistics for 208.117.244.183:
Packets: Sent = 71, Received = 64, Lost = 7 (9% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 3990ms, Average = 608ms
Control-C
^C

Collapse -
The thing about ping.
by R. Proffitt Forum moderator / May 27, 2014 1:02 AM PDT
In reply to: Ping test

At some point many are using that what if the ISP degrades ping packets to get the real data through?

Collapse -
If this is the case
by Adventi / June 7, 2014 10:17 PM PDT
In reply to: The thing about ping.

You need to ask if your ISP is using any types of QOS or Traffic shaping through the network. Ask for it in a official statement.

Aaron

Collapse -
Net Neutrality and more. You can't get a straight answer.
by R. Proffitt Forum moderator / June 8, 2014 1:06 AM PDT
In reply to: If this is the case

In the news, a load of lies from all parties it seems.

Collapse -
Traffic Shaping
by Adventi / June 8, 2014 2:26 AM PDT

Traffic shaping during peak times I believe is fair. Why should a normal broadband user be affected because someone wants to download 24/7 when they only use there internet for emails etc.

Unlimited BB is good, however it must have restrictions as its unfair if x amount of people are congesting the circuit when there is 10000 people being affected because of this x amount of people.

Anyhow, traffic shaping will be used in conjunction with high download traffic. If your not a 24/7 downloading it probably will have no affect on the circuit.

I haven't read into Net Neutrality however I know that the providers in England are at present very trustful about restrictions (at least Virgin Media and Daisy Communications)

I have Virgin Media at home, I can tell when I have had traffic management done to my circuit and its in the exact time scales they state on there contract. Which is fair and understandable.

Daisy Communications I personally work with and know for sure they have no such thing as traffic shaping. Except QOS for enhanced services and where customer wants to prioritize voice traffic etc.

Aaron

Collapse -
Use this info
by Adventi / June 7, 2014 10:16 PM PDT
In reply to: Ping test

Hey guys,

Sorry about the late reply, this information is good.

The main thing you want to highlight is that the ms is hitting at times upto 3990ms...This is ridiculous and should be sorted out by the ISP.

Focus on the packet loss and the latency with providing this information and the traceroute previously highlighting the potential bottleneck in the network.

Aaron

Collapse -
Also please note
by Adventi / June 7, 2014 10:23 PM PDT
In reply to: Use this info

Too add-on as I really want to make this clear.

If you are getting slow speeds and potentially intermittent connection, I have seen plenty of technical people miss diagnose these faults, if this was my case and I had to deal with it I would ensure that the following has been confirmed.

A) The speed of the circuit with throughput (if this is slow then you need to check the sync rate speed) Also ensure its done by wired with only one computer connected to the network to ensure fair test.
B) If the circuit is intermittent then this would ccause slow sync speeds by DLM if internet works the same in America and considering we have some circuits there it does for at least us. Slow sync speeds would then close slow speeds which therefore could potentially show packet loss and high latency caused by the actual physical line. At present, we are only taking diagnostic steps towards the network however please note that we should never ever forget the basics.

Aaron

Popular Forums
icon
Computer Newbies 10,686 discussions
icon
Computer Help 54,365 discussions
icon
Laptops 21,181 discussions
icon
Networking & Wireless 16,313 discussions
icon
Phones 17,137 discussions
icon
Security 31,287 discussions
icon
TVs & Home Theaters 22,101 discussions
icon
Windows 7 8,164 discussions
icon
Windows 10 2,657 discussions

CNET FORUMS TOP DISCUSSION

Help, my PC with Windows 10 won't shut down properly

Since upgrading to Windows 10 my computer won't shut down properly. I use the menu button shutdown and the screen goes blank, but the system does not fully shut down. The only way to get it to shut down is to hold the physical power button down till it shuts down. Any suggestions?