Hi Gottfried,
Thanks for the update - and sorry to hear that the problem persists. I googled around and it seems that Comcast has a long history of DNS troubles. See, for instance, this blog entry:
Why Comcast is chasing DNS outages
Posted by Phil Windley, April 15, 2005
blogs.zdnet.com
Here's a page which seems to be current, the author hasn't been able to access Yahoo! pages like you:
Who stole my Internet?
January 13, 2006? (Date extracted from source code)
shorenewstoday.com
The author mentions a broadband news and discussion site, broadbandreports.com There are a couple of threads of Comcast users with DNS problems, e.g.
[Connectivity] "Page not found" errors - Sunnyvale
dslreports.com
There seem to be two major factors. Comcast has an insufficient setup of its DNS system. Additionally it frequently is the target of "pharming" attacks. en.wikipedia.org
Speed is NOT everything, in fact it's useless if the DNServer doesn't work reliably.
I see nothing wrong with using non-Comcast DNServers, as a temporary fix or permanently. Berkeley as a provider of one of them has a long history of offering very useful code and services to the public.
Personally I have set up a small home server (Debian Linux-based) which acts as a gateway to the Net and has its own DNS, BIND - short for "Berkeley Internet Name Domain". bind9.net That way I am less dependent on possibly fragile DNS operation of my ISP. |
