dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1089
share rss forum feed

thataboi

join:2004-03-09
Springfield, OR

DNS issues.

Anyone else out West coast having Comcast DNS issues? Sometimes regular common websites such as google.com won't even load or load only text. I then run tracert and pings etc and find that 75.75.75.75 and 75.75.76.76 I are having packet loss. Anybody know of other dns servers out here we can use besides these two crappy ones and without compromising dnssec??


bradyr
Columbia College IT
Premium
join:2008-10-27
Sonora, CA

1 edit

1 recommendation

75.75.75.75 and 75.75.76.76 crappy? just because they aren't responding to pings means they are crappy, I forward to 75.75.75.75 since i'm on the west coast and i've had zero problems with DNS resolution. very snappy on every lookup.

Delayed ninja edit: Comcast most likely rate-limits ICMP packets on their dns servers. ping and traceroute are not the best way to judge DNS server performance. use tools like nslookup and dig to see how your dns performance is. I choose comcast's servers because they are only a couple hops from me and they perform lookups just as fast as google's dns servers.


RR Conductor
NWP RR Inc.,serving NW CA
Premium
join:2002-04-02
Redwood Valley, CA
kudos:1
reply to thataboi
I haven't seen any problems up here in Northwestern California (Mendocino County).
--



jlivingood
Premium,VIP
join:2007-10-28
Philadelphia, PA
kudos:2

1 edit

1 recommendation

reply to bradyr
said by bradyr:

Delayed ninja edit: Comcast most likely rate-limits ICMP packets on their dns servers. ping and traceroute are not the best way to judge DNS server performance. use tools like nslookup and dig to see how your dns performance is.

In response to the delayed ninja edit... Ninja bonus points for correctness and style. Bonus 2 throwing stars.

--
JL
Comcast


JigglyWiggly

join:2009-07-12
Pleasanton, CA
If you want to test dns
use dnsbenchmark
»www.grc.com/dns/benchmark.htm


egeek84
Premium
join:2011-07-28
Livermore, CA
reply to jlivingood
LOL!!!!!!!

thataboi

join:2004-03-09
Springfield, OR
reply to jlivingood
Typical dslreports critcism. Well did you use a dsnlookup tool?? Wow really? What is a dsntool going to tell me that I don't already know hen I am sitting in front of a screen with half the internet loading text?? So I did a simple tracert to the server as this was happening and it ended with packet loss. So are you going to insult me some more?

8 14 ms * 15 ms cdns01.comcast.net [75.75.75.75]


pflog
Bueller? Bueller?
Premium,MVM
join:2001-09-01
El Dorado Hills, CA
kudos:3
said by thataboi:

Typical dslreports critcism. Well did you use a dsnlookup tool?? Wow really? What is a dsntool going to tell me that I don't already know hen I am sitting in front of a screen with half the internet loading text?? So I did a simple tracert to the server as this was happening and it ended with packet loss. So are you going to insult me some more?

8 14 ms * 15 ms cdns01.comcast.net [75.75.75.75]

latency (typically gauged by a ping or traceroute) to a server that rate limits or drops ICMP and even udp traceroute packets is not a good way to check the response time of a DNS server.

The actual time it takes for a response is:

RTT (latency)
+
Lookup time (which may involve querying authoritative servers, or doing a recursive lookup, etc)

So even if a DNS server didn't rate limit ICMP, ping alone will not tell you the whole story.
--
"I drank what?" -Socrates


bradyr
Columbia College IT
Premium
join:2008-10-27
Sonora, CA

1 edit
reply to thataboi
When I mentioned that comcast dns servers do ICMP rate limiting, that means that they may not respond to ping requests and may also show timeout blips on traceroutes.

again, try using dig or nslookup to verify if you are having DNS issues.

traceroute and ping blips to 75.75.75.75 or 75.75.76.76 prove absolutely nothing due to their ICMP rate limiting. I will get the same "packet loss" that you do and I can guarantee you that my internet connection is having zero issues.

Edit: In case anyone was wondering what a typical dig response at 75.75.75.75 would look like:

ryan@skynet:~$ dig @75.75.75.75 google.com
 
; <<>> DiG 9.8.1-P1 <<>> @75.75.75.75 google.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10620
;; flags: qr rd ra; QUERY: 1, ANSWER: 11, AUTHORITY: 0, ADDITIONAL: 0
 
;; QUESTION SECTION:
;google.com.                    IN      A
 
;; ANSWER SECTION:
google.com.             211     IN      A       74.125.224.39
google.com.             211     IN      A       74.125.224.37
google.com.             211     IN      A       74.125.224.32
google.com.             211     IN      A       74.125.224.34
google.com.             211     IN      A       74.125.224.33
google.com.             211     IN      A       74.125.224.46
google.com.             211     IN      A       74.125.224.41
google.com.             211     IN      A       74.125.224.36
google.com.             211     IN      A       74.125.224.40
google.com.             211     IN      A       74.125.224.35
google.com.             211     IN      A       74.125.224.38
 
;; Query time: 19 msec
;; SERVER: 75.75.75.75#53(75.75.75.75)
;; WHEN: Tue Jan 22 17:16:18 2013
;; MSG SIZE  rcvd: 204
 

and here's a nslookup against 75.75.75.75:

ryan@skynet:~$ nslookup google.com 75.75.75.75
Server:         75.75.75.75
Address:        75.75.75.75#53
 
Non-authoritative answer:
Name:   google.com
Address: 74.125.224.39
Name:   google.com
Address: 74.125.224.37
Name:   google.com
Address: 74.125.224.32
Name:   google.com
Address: 74.125.224.34
Name:   google.com
Address: 74.125.224.33
Name:   google.com
Address: 74.125.224.46
Name:   google.com
Address: 74.125.224.41
Name:   google.com
Address: 74.125.224.36
Name:   google.com
Address: 74.125.224.40
Name:   google.com
Address: 74.125.224.35
Name:   google.com
Address: 74.125.224.38