ryanmcv
join:2001-10-14
Lemont, IL
 ·Comcast
 ·AT&T CallVantage
| Comcast DNS Servers Lagging AGAIN
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? |
|
hyphen
Premium
join:2004-08-29
Ventnor City, NJ | 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 |
|
teddystacker
join:2001-12-08
Philadelphia, PA
1 edit | reply to ryanmcv
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.. |
|
camarozz2828
join:2003-07-17
Hanover, MA | reply to ryanmcv
4.2.2.1 - 4.2.2.6 Are Level3 DNS Servers not Verizon... |
|
Big_D
Premium
join:2003-06-02
Augusta, GA
1 edit | reply to ryanmcv
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!
|
|
Blam
Penguin Power
Premium
join:2002-02-06
Philadelphia, PA | reply to camarozz2828
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  |
|
prestonlewis
Premium,MVM
join:2003-04-13
Sacramento, CA
·VoiceStick
·Comcast
 ·Pacific Bell - SBC
·DSL EXTREME
·Vonage
·VoicePulse
| reply to ryanmcv
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 |
|
vizionblind
join:2002-01-19
Bealeton, VA | reply to ryanmcv
so why should we stick with obtain automatically, when the other dns servers are better? |
|
ryanmcv
join:2001-10-14
Lemont, IL
·Comcast
·AT&T CallVantage
| reply to Big_D
said by 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. It's amazing how it was happening for EVERY site I pinged. |
|
Morty
Premium
join:2004-09-18 | Try using IP, you will find that there is little difference. There are far too many DNS paranoid people. |
|
chsdgfsdg
join:2001-12-31
Beverly Hills, CA
| reply to Big_D
said by 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. 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 |
|
Blam
Penguin Power
Premium
join:2002-02-06
Philadelphia, PA | It matters if the path to it is misconfigured or congested and the path to other DNS servers isn't. |
|
ryanmcv
join:2001-10-14
Lemont, IL
1 edit | 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! |
|
Blam
Penguin Power
Premium
join:2002-02-06
Philadelphia, PA | ^ 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. |
|
Qumahlin
Never Enough Time
Premium,MVM
join:2001-10-05
united state
1 edit | reply to Blam
said by Blam :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 |
|
Big_D
Premium
join:2003-06-02
Augusta, GA | Thank you! |
|
Blam
Penguin Power
Premium
join:2002-02-06
Philadelphia, PA
| reply to Qumahlin
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. |
|
Big_D
Premium
join:2003-06-02
Augusta, GA
| 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! |
|
Qumahlin
Never Enough Time
Premium,MVM
join:2001-10-05
united state
| reply to Blam
said by Blam :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 |
|
Blam
Penguin Power
Premium
join:2002-02-06
Philadelphia, PA | reply to Big_D
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. |
|
