Re: Comcast DNS Servers Lagging AGAIN in Comcast HSI http://www.dslreports.com/forum/r13138322 en Sun, 29 Nov 2009 08:05:06 EDT Sun, 29 Nov 2009 08:05:06 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13148845 priller :
said by Big_D See Profile:

You obviously don't understand how it works. I would suggest doing a little research before posting. ICMP packets do not go to the DNS server, they only go to the destination as requested by your traceroute or ping. If a DNS lookup is required, it is done before the ping or traceroute is attempted.
I glad somebody understands.

This is one pointless thread.]]> http://www.dslreports.com/forum/remark,13148845 Tue, 12 Apr 2005 07:39:16 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13148605 Galvage :
said by floydb_1982 See Profile:

How do I switch from the Comcast DNS servers over to the Verizon DNS servers?
If you are using a router you want to go to the WAN settings and select the manual setting for setting DNS servers.

If you are connecting directly to the Modem from your computer then I reccomend looking on google or on just about any major ISP help page like Earthlink]]> http://www.dslreports.com/forum/remark,13148605 Tue, 12 Apr 2005 05:45:01 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13148464 floydb_1982 : How do I switch from the Comcast DNS servers over to the Verizon DNS servers?]]> http://www.dslreports.com/forum/remark,13148464 Tue, 12 Apr 2005 04:24:38 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13148343 Galvage : The trick is that most internet sites work based on names of the next page and links associated with it rather than with specific ips. Ie www.yahoo.com is really 66.94.230.34 but everything in it is yahoo.com/***** so if you have a good dns server you will get page load times of under half a second rather than over 1 second.

Earthlinks DNS servers out of everyones have given me the best overall results for webrowsing. It is literally a difference that the average user can see. Its literally a night and day difference. Its not the ping times that make the difference its the DNS resolve times that make the difference.

My first ping to www.yahoo.com with comcast DNS servers is roughly 100-120ms which equates to roughly 1/10th of a second. Yahoo has 3-4 sites that it must resolve just loading the main page. which means that it will take at least 3-4 10ths of a second just resolving each DNS and another 2-3 seconds to get the information So that equates to comcast dns server taking about 3 seconds to get the information.

My first ping using Earthlink DNS servers gets me 40-50ms which is 1/2 of the time it takes a comcast DNS server to do the job.

This means that it will spend less time getting the initial information 1-2 10ths of a second are used to resolve the DNS. This means that you will likely see your pages load in roughly 2- 2.5 seconds rather than the comcast 3 seconds. Human eye can literally see the difference.

If comcast could bring thier DNS servers down to say a 50-60ms response then you will see more people using the comast dns servers. ]]> http://www.dslreports.com/forum/remark,13148343 Tue, 12 Apr 2005 03:22:40 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13148087 b1gdr3 : Some people on this forum won't be happy until they have 100mbit/100mbit and 1 nanosecond dns response time for $1.00 a month...quit bellyaching already.
--
I wasn't born with enough middle fingers.]]> http://www.dslreports.com/forum/remark,13148087 Tue, 12 Apr 2005 01:45:36 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13147782 mallyman : DNS only translates ip to hostname or hostname to ip... it has no effect whatsoever on the ping time... DNS also helps certain services (smtp) be found on the internet as well using things like MX records....]]> http://www.dslreports.com/forum/remark,13147782 Tue, 12 Apr 2005 00:44:44 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13147187 ryanmcv : I received the same results:

Default Server:  ns.cmc.co.denver.comcast.net
Address:  68.87.66.196
 
> www.yahoo.com
Server:  ns.cmc.co.denver.comcast.net
Address:  68.87.66.196
 
Non-authoritative answer:
Name:    www.yahoo.akadns.net
Addresses:  66.94.230.47, 66.94.230.34, 66.94.230.37, 66.94.230.43
          66.94.230.49, 66.94.230.42, 66.94.230.35, 66.94.230.32
Aliases:  www.yahoo.com
 
> server 68.87.64.196
Default Server:  ns.inflow.pa.bo.comcast.net
Address:  68.87.64.196
 
> www.yahoo.com
Server:  ns.inflow.pa.bo.comcast.net
Address:  68.87.64.196
 
Non-authoritative answer:
Name:    www.yahoo.akadns.net
Addresses:  216.109.118.70, 216.109.117.107, 216.109.118.71, 216.109.118.67
          216.109.118.73, 216.109.118.68, 216.109.118.64, 216.109.117.108
Aliases:  www.yahoo.com
]]> http://www.dslreports.com/forum/remark,13147187 Mon, 11 Apr 2005 23:17:33 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13146763 Big_D : Both of Comcast's national servers seem to be returning queries just fine for me. Can you ping them?

C:\>nslookup
(snip)
> server 68.87.66.196
Default Server:  ns.cmc.co.denver.comcast.net
Address:  68.87.66.196
 
> www.yahoo.com
Server:  ns.cmc.co.denver.comcast.net
Address:  68.87.66.196
 
Non-authoritative answer:
Name:    www.yahoo.akadns.net
Addresses:  66.94.230.35, 66.94.230.37, 66.94.230.38, 66.94.230.34
          66.94.230.42, 66.94.230.39, 66.94.230.49, 66.94.230.45
Aliases:  www.yahoo.com
 
> server 68.87.64.196
Default Server:  ns.inflow.pa.bo.comcast.net
Address:  68.87.64.196
 
> www.yahoo.com
Server:  ns.inflow.pa.bo.comcast.net
Address:  68.87.64.196
 
Non-authoritative answer:
Name:    www.yahoo.akadns.net
Addresses:  216.109.117.109, 216.109.118.77, 216.109.117.206, 216.109.117.107
          216.109.118.72, 216.109.117.204, 216.109.118.79, 216.109.118.78
Aliases:  www.yahoo.com

--
You want the truth? You can't handle the truth! ]]> http://www.dslreports.com/forum/remark,13146763 Mon, 11 Apr 2005 22:24:51 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13146223 ryanmcv : It's happening again tonight -- Using Comcast's DNS servers, I cannot access ANY sites. Using the 4.2.2.2/3 servers, I can access all sites just fine.]]> http://www.dslreports.com/forum/remark,13146223 Mon, 11 Apr 2005 21:24:31 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13145574 TKJunkMail :
said by rwarrin991 See Profile:

Can someone tell me how to change the dns servers, I would like to make that change but not sure how to do it.

Thanks
Here is a link with a sample that assigns DNS to 1 Comcast DNS server and 1 level3 DNS server.
»Re: [DNS] DNS Outage is Resolved - Please Read]]> http://www.dslreports.com/forum/remark,13145574 Mon, 11 Apr 2005 20:13:47 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13145563 Big_D : Here you go: »Comcast High Speed Internet FAQ »How do I change what DNS server my computer uses?]]> http://www.dslreports.com/forum/remark,13145563 Mon, 11 Apr 2005 20:12:06 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13145419 rwarrin991 : Can someone tell me how to change the dns servers, I would like to make that change but not sure how to do it.

Thanks]]> http://www.dslreports.com/forum/remark,13145419 Mon, 11 Apr 2005 19:59:21 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13144607 ricksr : If the difference between 30 and 80ms makes that much difference in someones life then there's a bigger issue to deal with and it aint the internet. Can't we all get along?]]> http://www.dslreports.com/forum/remark,13144607 Mon, 11 Apr 2005 18:17:49 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13143971 thisismyname1 : I haven't used Comcast DNS servers since that other day when they were horrible. I will change them by the end of the month and hope its fixed by then.
--
Freedom of expression should not be hampered by the unwillingness of others to accept things.-NinjaMaster]]> http://www.dslreports.com/forum/remark,13143971 Mon, 11 Apr 2005 17:00:03 EDT Re: msg deleted http://www.dslreports.com/forum/remark,13143093 sortofageek : Could everyone, please, look at the thread title, understand the topic and return to that topic?

There is always the HeyMod button if you think we have missed something.

»Site FAQ »Hey Mods - what is it?
--
Team Helix Forum - Join Us?]]> http://www.dslreports.com/forum/remark,13143093 Mon, 11 Apr 2005 15:16:56 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13142641 mdmaddox : I think the bottom line is the original poster was having a problem and switching DNS servers helped. The problem could be a lot of things. But what the definition of is is or lagging or lag has gotten out of hand. Take a break and see if they post back. Not everyone lives 24/7 on this forum.:D]]> http://www.dslreports.com/forum/remark,13142641 Mon, 11 Apr 2005 14:10:05 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13142640 Blam : To say it "has no use" is your own personal opinion, IMHO. There were some clarification points brought out and IMHO, to keep starting endless threads saying the same thing that would end up being locked for redundancy, rather than keeping the issue to a single thread, is a waste of server space IMHO. But that will be up to the Mods I expect. ;)]]> http://www.dslreports.com/forum/remark,13142640 Mon, 11 Apr 2005 14:09:59 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13142565 Morty : None of the last page and a half of this thread have been of any use. Honestly look. All it has been is a giant conversation with three forum members saying one thing and you saying another -- of no use to this thread's topic. Either the poster can provide proof or an explanation as to what's "Lagging" with Comcasts DNS or it this thread is going to go downhill even more. From what I can see, as there's been no real discussion about this threads topic, he can create a new thread with all the technical details as to what he exactly means by "lagging" his proof, tests etc. and from that point we can help him or have a healthy discussion on the topic. Currently, the last page and a half have been no use to anyone.]]> http://www.dslreports.com/forum/remark,13142565 Mon, 11 Apr 2005 13:58:50 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13142472 Blam : Just because the original poster didn't immediately respond back within some instant amount of time, then the thread should be locked? I guess that's like how Comcast closes tickets when a customer's problems still haven't been solved because the tech didn't know what else to do?

Threads like this are of interest to me regarding ancillary info that might get posted, considering that right at 1:18 pm, my connection went poof and I'm back on Verizon! Got about 8 hours worth of good connection and away it went.

Edit to clarify and count correctly: Only 6 hours of connection. ;) From 7 am - ~1 pm.]]> http://www.dslreports.com/forum/remark,13142472 Mon, 11 Apr 2005 13:45:52 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13142041 Blam : It seems the dead horse is going to be beaten some more.

My comments have to do with the original poster's use of the term "lagging" and what that means to certain people in the internet community who are gamers and who will bemoan the fact that they are connected to a game server and their persona in the game suddenly "hangs" and when they can move again, they're "dead". And as a troubleshooting measure when this happens, most of the game software that has a corresponding ability to operate over a network, uses "ping" to indicate what the general network environment is like and whether there is congestion and latency. I have myself gamed online (UT), so I am aware of the usaage of that term to describe slowness, hangs, and disconnects.

And to assume that the entire Comcast subscribership knows about this place, let alone is willing to complain here or even bother calling up the Call Center... or even spends as much time on a computer as many of the posters here (who are obviously more clued into sites like this to post questions to and try to troubleshoot because it is part of their hobbies or jobs), is a bit disingenous. Many who are working spend more time on the computers at work doing surfing, emailing, etc., than at home and the worksite IT folks like myself, get the hits to keep everything running smoothly.

I have 2 sisters subscribed to Comcast HSI in 2 different counties from mine and each other and neither are on their machines as a hobby/job like I am. And because I've been involved in various distributed computing projects for the past 6 years, my network link "from here to there" is more important to me than their getting to email or browsing a few websites is to them, particularly since they can often do that kind of stuff at work during lunch, etc. And thus I wouldn't expect them to immediately find this place to post complaints to or call up Comcast if something has gone horribly wrong for them. They'll just turn off the machine and go do something else.

So to say that "no one else is complaining" is not telling you the whole picture, IMHO.]]> http://www.dslreports.com/forum/remark,13142041 Mon, 11 Apr 2005 12:42:20 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13141768 Morty : I think you, like many people on this forum are confusing unrelated problems with DNS. There's nothing wrong with the Comcast DNS servers, the entire united states using Comcast uses these servers, if there was an issue like there was last week, then you'd have another 30,000 people reading these posts. Now in your case, I have seen several posts from PA on this forum from people who appear to be having a DNS issue, however it's not, it would most likely be a routing issue to the DNS servers for your area. This does not mean there is a problem with the DNS or DNS servers. As if it were a problem with the DNS servers the entire nation would be affected. I'm questioning if it is even a routing issue to the server, as if this was the case you would still see more posts here about it. It could be something localized right to your market/area of PA It would take more troubleshooting to determine.]]> http://www.dslreports.com/forum/remark,13141768 Mon, 11 Apr 2005 11:57:08 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13141635 Blam : Yes - the term "lagging" IS in the title and as I indicated, there's a whole subculture who uses it to describe a specific environment, whether it really applies to the situation or not. ;)

And yes, I think we have beat the horse to a pulp. ;)]]> http://www.dslreports.com/forum/remark,13141635 Mon, 11 Apr 2005 11:39:19 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13141591 Qumahlin :
said by Blam See Profile:

said by Qumahlin See Profile:

We are NOT talking about the ping time to the name server? Are you completely ignorant to what the OP's very first post is?

The op states "Using Comcast's DNS servers, I seem to be getting 50-60ms pings to almost all sites (such as www.comcast.net). I switched over to 4.2.2.2 and 4.2.2.3 (Verizon's DNS servers I believe) and now I'm running great again (30ms pings to www.comcast.net). Is anyone else having issues?"

Do you not understand what the OP is claiming? The OP is claiming that his ping times to COMCAST.NET (comcasts portal site...not their DNS server) change based on what his DNS server is set too....
I understand and I also understand the oft-used terminogy of what "lag" refers to. Which goes back to my original comments about the routing issues that Comcast has and getting a quick reponse back. You yourself even talked about "faster" browsing.
The only place "lag" is mentioned is in the thread title. Therefore i'm assuming the OP thinks the DNS server is lagging because they think that their ping times are varying based on the DNS server they are using which it does not.

Can we just let this thread die now :P
--
Forum Posts:6500]]> http://www.dslreports.com/forum/remark,13141591 Mon, 11 Apr 2005 11:32:43 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13141519 Blam :
said by Qumahlin See Profile:

We are NOT talking about the ping time to the name server? Are you completely ignorant to what the OP's very first post is?

The op states "Using Comcast's DNS servers, I seem to be getting 50-60ms pings to almost all sites (such as www.comcast.net). I switched over to 4.2.2.2 and 4.2.2.3 (Verizon's DNS servers I believe) and now I'm running great again (30ms pings to www.comcast.net). Is anyone else having issues?"

Do you not understand what the OP is claiming? The OP is claiming that his ping times to COMCAST.NET (comcasts portal site...not their DNS server) change based on what his DNS server is set too....
I understand and I also understand the oft-used terminogy of what "lag" refers to. Which goes back to my original comments about the routing issues that Comcast has and getting a quick reponse back. You yourself even talked about "faster" browsing.]]> http://www.dslreports.com/forum/remark,13141519 Mon, 11 Apr 2005 11:21:47 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13141496 Qumahlin : We are NOT talking about the ping time to the name server? Are you completely ignorant to what the OP's very first post is?

The op states "Using Comcast's DNS servers, I seem to be getting 50-60ms pings to almost all sites (such as www.comcast.net). I switched over to 4.2.2.2 and 4.2.2.3 (Verizon's DNS servers I believe) and now I'm running great again (30ms pings to www.comcast.net). Is anyone else having issues?"

Do you not understand what the OP is claiming? The OP is claiming that his ping times to COMCAST.NET (comcasts portal site...not their DNS server) change based on what his DNS server is set too....
--
Forum Posts:6500]]> http://www.dslreports.com/forum/remark,13141496 Mon, 11 Apr 2005 11:17:35 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13141431 Blam :
said by Qumahlin See Profile:

said by Blam See Profile:

Read my edited response to your edited response.
Bottom line is the poster has shown no evidence of the DNS server "lagging" in any way shape or form. If they'd like to post further information in relation to the DNS server lagging (Since nothing they've posted as of yet points to that) then fine.

My previous posts still stand, the DNS servers have nothing to do with the OP's ping times as he seems to think they do
You are still not understanding the subculture use of the term "lagging". As an example, I did a couple of traces using this site: »network-tools.com/

Where going from that site to the Denver name server, you get:

TraceRoute to 68.87.66.196 [ns.cmc.co.denver.comcast.net]
Hop (ms) (ms) (ms) IP Address Host name
1 3 0 3 66.98.244.1 gphou-66-98-244-1.ev1.net
2 2 0 0 66.98.241.4 gphou-66-98-241-4.ev1.net
3 0 0 0 66.98.240.6 gphou-66-98-240-6.ev1.net
4 1 1 1 129.250.10.229 ge-2-1-0.r02.hstntx01.us.bb.verio.net
5 10 10 10 129.250.5.100 p16-0-3-0.r21.dllstx09.us.bb.verio.net
6 213 254 212 129.250.9.38 p16-0.att.dllstx09.us.bb.verio.net
7 11 11 12 12.123.17.86 tbr2-p014001.dlstx.ip.att.net
8 60 60 63 12.122.12.126 gbr4-p30.dvmco.ip.att.net
9 59 59 60 12.122.1.42 -
10 59 59 60 12.123.36.149 gar3-p370.dvmco.ip.att.net
11 60 60 60 12.124.157.54 -
12 61 61 61 12.244.71.14 -
13 66 65 66 68.87.66.196 ns.cmc.co.denver.comcast.net

Now from someone casually looking at the above, you see pings of 1s, 5s, 10s, etc., from the intitiating location, and then suddenly it's as if it gets into the Comcast network and you have the steady 50s and 60s.

For folks who are gamers, the above would be considered a "lag", despite it being consistent throughout.

EDIT:

You edited again and how can you assume that the use of the terminology has nothing to do with anything? That is quite dismissive when you have folks who use terms in different ways and not being aware of those uses is why miscommunications happen.]]> http://www.dslreports.com/forum/remark,13141431 Mon, 11 Apr 2005 11:09:01 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13141396 Qumahlin :
said by Blam See Profile:

Read my edited response to your edited response.
Bottom line is the poster has shown no evidence of the DNS server "lagging" in any way shape or form. If they'd like to post further information in relation to the DNS server lagging (Since nothing they've posted as of yet points to that) then fine.

My previous posts still stand, the DNS servers have nothing to do with the OP's ping times as he seems to think they do. That is the issue he posted, that is the issue I answered. the terminology of "lagging" has nothing to do with this other then the OP's misinterpretation of the data he is seeing
--
Forum Posts:6500]]> http://www.dslreports.com/forum/remark,13141396 Mon, 11 Apr 2005 11:03:31 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13141379 Blam : Read my edited response to your edited response.]]> http://www.dslreports.com/forum/remark,13141379 Mon, 11 Apr 2005 11:01:16 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13141352 Qumahlin :
said by Blam See Profile:

In that particular case, is that not what an "average" user would like to see? Faster browsing times rather than timeouts? And those who know about the few rudimentary net tools who want to try to troubleshoot why they get web page timeouts and slow loading for almost every site (and yes, I know that some websites can be borked giving a slow response to http requests), will usually pull out the old ping/traceroute commands to see if those indicate something that might be amiss. Ie., if they can't ping the website name then they can go to step b, trying the address, and if they can't ping that, then chances are the problem may be local, etc., and they can go from there.
That has nothing to do with the topic. We aren't talking about an average user and their troubleshooting steps. We aren't talking about site timeouts, we aren't talking about delayed responses.

We are talking about the OP who states clearly that they get faster ping times to comcast.net when they are using the level 3 DNS servers versus the Comcast DNS servers and then using this incorrect information to form the basis of a "well the Comcast DNS servers must clearly be lagging" when in reality the DNS server has NOTHING to do with their ping time.

--
Forum Posts:6500]]> http://www.dslreports.com/forum/remark,13141352 Mon, 11 Apr 2005 10:56:49 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13141331 Blam : In that particular case, is that not what an "average" user would like to see? Faster browsing times rather than timeouts? And those who know about the few rudimentary net tools who want to try to troubleshoot why they get web page timeouts and slow loading for almost every site (and yes, I know that some websites can be borked giving a slow response to http requests), will usually pull out the old ping/traceroute commands to see if those indicate something that might be amiss. Ie., if they can't ping the website name then they can go to step b, trying the address, and if they can't ping that, then chances are the problem may be local, etc., and they can go from there.

EDIT: Since you edited after I started replying. In reference to your edited-in statement:

You say this "It matters if the path to it is misconfigured or congested and the path to other DNS servers isn't" You didn't reply to any specific post so one would think your statement is made to say that you are agreeing with the OP that by changing his DNS server he changed his ping times, which is wrong.
So who is this "no one" who supposedly doesn't understand what I am saying? It seems there are folks posting here who are getting the gist of what I am saying and have been basically saying similar for the past couple weeks in multiple posts here - something that has come to a crescendo over the past week. I am not trying to obfuscate the point like you seem to be doing.

When someone says "lagging", that is a terminology often used by gamers who often talk about games "lagging" and there is a whole subculture of the use of "ping" in order to determine how well your connection to a game server is. And "lags" often have to do with congestion somewhere between the gamer's machine and the game server. So yes, I am addressing this post in terms of the common use of the term "lagging".]]> http://www.dslreports.com/forum/remark,13141331 Mon, 11 Apr 2005 10:54:16 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13141273 Qumahlin :
said by Blam See Profile:

I am talking about getting the information FROM the DNS, BACK to the requesting machine. It can have that answer in record time... But if that information gets lost while trying to get back to my machine, then there is a problem, don't you think? Having names/addresses cached locally helps in that instance, as I don't even have to make the request to an outside machine.

As I noted to Big_D - there are essentially 2 different issues being brought out in this thread. The machine itself and the routes to/from that machine. The DNS can blab blab blab and its blabbing goes nowhere. I can ask ask ask and never get a response - IF something is wrong with my pipe from here to there.
I am addressing the issue of the OP saying that his ping times are lower when he uses the Level 3 servers, versus when he uses the Comcast servers.

Changing your DNS server might effect your web browsing speed, but it does not effect your ping times.

You say this "It matters if the path to it is misconfigured or congested and the path to other DNS servers isn't" You didn't reply to any specific post so one would think your statement is made to say that you are agreeing with the OP that by changing his DNS server he changed his ping times, which is wrong.

the statement of "It matters if the path to it is misconfigured or congested and the path to other DNS servers isn't" has no bearing on ping times other then the ping time to the DNS server which has nothing to do with the ping time to the site your running a ping/tracert to.

There is that clarified enough? The problem to begin with was that your statement caused the OP to believe that a congested DNS server or misconfigured path to the DNS server has anything to do with his ping time to other sites.

Hence his response of "ding ding we have a winner"

--
Forum Posts:6500]]> http://www.dslreports.com/forum/remark,13141273 Mon, 11 Apr 2005 10:46:25 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13140909 Middleburg : Ill say this DNS switch made my pings go from 80 ms to 80 ms, so no help whatsoever.]]> http://www.dslreports.com/forum/remark,13140909 Mon, 11 Apr 2005 09:47:15 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13140900 Blam : I am talking about getting the information FROM the DNS, BACK to the requesting machine. It can have that answer in record time... But if that information gets lost while trying to get back to my machine, then there is a problem, don't you think? Having names/addresses cached locally helps in that instance, as I don't even have to make the request to an outside machine.

As I noted to Big_D - there are essentially 2 different issues being brought out in this thread. The machine itself and the routes to/from that machine. The DNS can blab blab blab and its blabbing goes nowhere. I can ask ask ask and never get a response - IF something is wrong with my pipe from here to there.]]> http://www.dslreports.com/forum/remark,13140900 Mon, 11 Apr 2005 09:44:51 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13140878 Blam : You aren't understanding what I am saying either. One of the discussions here has to do with ping times to the destination machine. I would ask that you separate out the issues being discussed.]]> http://www.dslreports.com/forum/remark,13140878 Mon, 11 Apr 2005 09:41:00 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13140845 Qumahlin :
said by Blam See Profile:

Like I said, the DNS can be the biggest fastest in the world but if you can't get to it consistently, because the pings go all over the place depending on the moment, it's useless.

This denial of the problems is why they never get resolved.
This has nothing to do with "denial" of a problem. Bottom line is a DNS server no matter how slow, flaky, broken has no effect on your ping times, nor your route to the host.

DNS is just what it's acronym stands for "Domain Name Server" It takes a Domain name and looks up it's Registered IP in order for your browser to contact the site. It will not effect the speed of your pings.

Yes a crappy DNS server will cause web browsing to be slower of course because your browser has to constantly wait for the DNS server to complete it's lookup so that the browser can have the IP to actually contact the site.

But irregardless of how long it takes the DNS server to complete the operation it does not factor into your ping time whatsoever
--
Forum Posts:6500]]> http://www.dslreports.com/forum/remark,13140845 Mon, 11 Apr 2005 09:35:36 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13140838 Big_D : You obviously don't understand how it works. I would suggest doing a little research before posting. ICMP packets do not go to the DNS server, they only go to the destination as requested by your traceroute or ping. If a DNS lookup is required, it is done before the ping or traceroute is attempted.
--
You want the truth? You can't handle the truth! ]]> http://www.dslreports.com/forum/remark,13140838 Mon, 11 Apr 2005 09:35:06 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13140805 Blam : Because this damn network is screwed up right now (and the routing problems in several areas have been acknowledged), it might be able to resolve at the beginning of the trace (or better, if one has the name/address cached locally, then it assumes it exists), but then ICMP packets have been dropped or hung up somwhere, trying to get to the DNS destination or often any other location for that matter. Like I said, the DNS can be the biggest fastest in the world but if you can't get to it consistently, because the pings go all over the place depending on the moment, it's useless.

This denial of the problems is why they never get resolved.]]> http://www.dslreports.com/forum/remark,13140805 Mon, 11 Apr 2005 09:30:50 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13140793 Big_D : Thank you!]]> http://www.dslreports.com/forum/remark,13140793 Mon, 11 Apr 2005 09:29:19 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13140724 Qumahlin :
said by Blam See Profile:

It matters if the path to it is misconfigured or congested and the path to other DNS servers isn't.
No it doesn't because the trace does not BEGIN until the DNS is resolved.

You can have the slowest, most underpowered DNS server in the world and your ping times to sites will remain the same because name resolution has nothing to do with response time other then the initial query and then the name queries of the hops your route takes.

So unless your tracert program is actually pausing it's operation while waiting for DNS lookup and adding it's pause time into your ping calculations a slow DNS server will have NO effect on ping times.

--
Forum Posts:6500]]> http://www.dslreports.com/forum/remark,13140724 Mon, 11 Apr 2005 09:16:18 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13140657 Blam : ^ Yeah. You can have the fastest, most powerful and most responsive DNS server in the world but if you can't get to it, then what is the point? It's just talking to itself. ;)]]> http://www.dslreports.com/forum/remark,13140657 Mon, 11 Apr 2005 09:04:46 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13140475 ryanmcv :
quote:
It matters if the path to it is misconfigured or congested and the path to other DNS servers isn't.

Ding Ding! We have a winner!]]> http://www.dslreports.com/forum/remark,13140475 Mon, 11 Apr 2005 08:20:54 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13140231 Blam : It matters if the path to it is misconfigured or congested and the path to other DNS servers isn't.]]> http://www.dslreports.com/forum/remark,13140231 Mon, 11 Apr 2005 06:47:57 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13139569 chsdgfsdg :
said by Big_D See Profile:

The speed at which a DNS server resolves a domain name has absolutely no affect on ping time. comcast.net has multiple IP addresses and locations, when you change DNS servers you also will likely resolve it to one of the other locations, which would of course explain the change in ping times.
That's what I thought, and before your post seeing everyone else think it matter made me start to question myself. Good thing you said that, I take your side against everyone on here. I'm no expert, but it seems to me that basic internet knowledge should tell you that the DNS servers don't matter in pig times.

Why would they? just doesn't make sense to think they have an affect. I don't think you people relize how internet transmissions work. You ping an IP not a name.
--
»www.imagecrown.com »www.crowntemplates.com]]> http://www.dslreports.com/forum/remark,13139569 Mon, 11 Apr 2005 01:53:53 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13139019 Morty : Try using IP, you will find that there is little difference. There are far too many DNS paranoid people.]]> http://www.dslreports.com/forum/remark,13139019 Mon, 11 Apr 2005 00:06:43 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13138583 ryanmcv :
said by Big_D See Profile:

The speed at which a DNS server resolves a domain name has absolutely no affect on ping time. comcast.net has multiple IP addresses and locations, when you change DNS servers you also will likely resolve it to one of the other locations, which would of course explain the change in ping times.
It's amazing how it was happening for EVERY site I pinged. ;)]]> http://www.dslreports.com/forum/remark,13138583 Sun, 10 Apr 2005 23:03:17 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13138322 vizionblind : so why should we stick with obtain automatically, when the other dns servers are better?]]> http://www.dslreports.com/forum/remark,13138322 Sun, 10 Apr 2005 22:25:47 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13138268 prestonlewis : As a long time Comcast user, former PacBell/SBC DSL user, and now a WISP user (along with Comcast HSI), I have found that from time to time my ISP providers DNS resolution will fail for one reason or another and for unpredictable periods of time. In my network settings, in the TCP/IP tab, and then the DNS tab, I usually have both my ISP DNS settings first, then I add the fastest Level 3 open server, which for me is 4.2.2.1, then the 2nd fastest Level 3 server, 4.2.2.3 That way, I have 4 DNS servers which can be acccessed if my ISP's go off line.

Another solutions is to use software like EZ DNS or another DNS caching program that will store the numerical DNS address for a web page's name in your computer for days or weeks so accessing a DNS server is unnecessary for commonly used web pages like www.google.com You can even tweak your computer's DNS settings to extend the time it will hold the information.

XP normally holds DNS settings for 24hours so it will only ask your DNS server for an address once in 24 hours. The setting is in the registry and can be made to last longer. Here is a page that describes how to do this:

»www.techiwarehouse.com/cms/engin···163e0b14]]> http://www.dslreports.com/forum/remark,13138268 Sun, 10 Apr 2005 22:18:19 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13138196 Blam : Yeah. I have actually used Verizon's local ones here in Philly at times as a backup since they are set on my DSL:

151.197.0.38/.39 ;)]]> http://www.dslreports.com/forum/remark,13138196 Sun, 10 Apr 2005 22:06:58 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13138164 Big_D : The speed at which a DNS server resolves a domain name has absolutely no affect on ping time. comcast.net has multiple IP addresses and locations, when you change DNS servers you also will likely resolve it to one of the other locations, which would of course explain the change in ping times.
--
You want the truth? You can't handle the truth!
]]> http://www.dslreports.com/forum/remark,13138164 Sun, 10 Apr 2005 22:03:00 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13138152 camarozz2828 : 4.2.2.1 - 4.2.2.6 Are Level3 DNS Servers not Verizon...]]> http://www.dslreports.com/forum/remark,13138152 Sun, 10 Apr 2005 22:00:56 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13137995 teddystacker : Yes,Same here in Philly.Found they were pretty slow right after people were claiming the issued was "fixed" , but dare not post as I would either get flamed or the post deleted or locked by one of the mods.

As I have posted before,Comcasts DNS servers have been slow (Compared with some other Isp's) for a long time - its just a issue that I have come to live with or bypassed by using a different one..]]> http://www.dslreports.com/forum/remark,13137995 Sun, 10 Apr 2005 21:39:13 EDT Re: Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13137977 hyphen : Wow your right when I'm using comcast dns i get around 70-80ms on Comcast.net. When I switch to 4.2.2.1 I get around 15-20ms]]> http://www.dslreports.com/forum/remark,13137977 Sun, 10 Apr 2005 21:35:47 EDT Comcast DNS Servers Lagging AGAIN http://www.dslreports.com/forum/remark,13137870 ryanmcv : Using Comcast's DNS servers, I seem to be getting 50-60ms pings to almost all sites (such as www.comcast.net). I switched over to 4.2.2.2 and 4.2.2.3 (Verizon's DNS servers I believe) and now I'm running great again (30ms pings to www.comcast.net). Is anyone else having issues?]]> http://www.dslreports.com/forum/remark,13137870 Sun, 10 Apr 2005 21:19:27 EDT