Comcast's DNS has really sucked lately

Post #336,756 by malraux 12/5/10 10:16:43 PM Reply	Comcast's DNS has really sucked lately After a few weeks of spotty, slow service, they went out completely tonight. I just reset the router to use OpenDNS and all the problems are gone. Regards, -scott Welcome to Rivendell, Mr. Anderson.
Post #336,757 by Another Scott 12/5/10 10:22:59 PM Reply	I've been using DNSAdvantage for a few months. It seems much, much faster than my cable provider's (Cox). I changed during the summer, I think, when it often seemed to be taking several seconds for each name resolution. Dunno if there are any issues in using such a service, but I figure I'm such a small-fry that it's not much to worry about. At least so far... I just noticed that Google has a free public DNS as well - http://code.google.com/speed/public-dns/ Cheers, Scott.
Post #336,761 by static 12/6/10 1:25:17 AM Reply	I remember when they announced that. You'd think that ISPs would pick up their game when that happened. Or maybe they were thinking "Meh - the knowledgeable will use them and stop bothering us". :-/ Wade. Q:Is it proper to eat cheeseburgers with your fingers? A:No, the fingers should be eaten separately.
Post #336,762 by Andrew Grygus 12/6/10 1:36:31 AM Reply	I use a Verizon DNS server a lot . . . . . because 4.2.2.2 and 4.2.2.1 are really easy to remember. The only other one I can remember is AT&T (former SBC (formerly PacBell)) 206.13.29.12 and 30.12 simply because I've used them for so many years. All these give pretty good response.
Post #336,784 by folkert 12/6/10 11:27:17 AM Reply	I've been using my stuff...
Post #336,796 by malraux 12/6/10 3:06:59 PM Reply	DNS benchmarking http://code.google.com/p/namebench/ Regards, -scott Welcome to Rivendell, Mr. Anderson.
Post #336,821 by Another Scott 12/6/10 7:51:15 PM Reply	Neat. Says I should be using my ISP's: 102% faster. :-/

Welcome to IWETHEY!