 jlivingoodPremium,VIP
join:2007-10-28
Philadelphia, PA
kudos:1 | reply to JJJohnson
Re: [DNS] Comcast DNS connectivity issues said by JJJohnson:Just how bad _are_ Comcast's DNS servers? I switched to them briefly today. The two servers assigned through DHCP were 75.75.75.76 and 75.75.75.75. While using them I was getting at least 20% failed DNS lookups just doing typical web browsing. Jeezus, even www.google.com failed. You must have some other issue. You might imagine that if 20% of all our customer DNS queries failed you would have a thousand people posting here and articles in the press.
Next time you have this issue, run dig at the command line and post the results here, as well as a traceroute to the IP of the server.
So, dig @75.75.75.75 www.google.com
and then dig @2001:558:FEED::1 www.google.com
and then traceroute 75.75.75.75
and then traceroute6 2001:558:FEED::1
- Jason
--
JL
Comcast |
|
 NetFixerFrom my cold dead handsPremium
join:2004-06-24
The Boro
 ·Comcast Business..
 ·Vonage
 ·Cingular Wireless
·Comcast
| said by jlivingood:said by JJJohnson:Just how bad _are_ Comcast's DNS servers? I switched to them briefly today. The two servers assigned through DHCP were 75.75.75.76 and 75.75.75.75. While using them I was getting at least 20% failed DNS lookups just doing typical web browsing. Jeezus, even www.google.com failed. You must have some other issue. You might imagine that if 20% of all our customer DNS queries failed you would have a thousand people posting here and articles in the press... Of course, if he did actually use 75.75.75.76 as one of the DNS servers, that would readily explain the query failures. 
--
We can never have enough of nature.
We need to witness our own limits transgressed, and some life pasturing freely where we never wander. |
|
| said by NetFixer:Of course, if he did actually use 75.75.75.76 as one of the DNS servers, that would readily explain the query failures. Naw, just copied the wrong IP. It was using DHCP, so whatever the IP addresses were handed out. |
|
