Been a while since Google launched its Public DNS service and having used it for that long, I felt it was very unreliable. I had issues opening websites that had a lot of external items in it, and the most frustrating experience was with BBC UK’s site whose newsimg sub-server failed to resolve when using their DNS – I do much news reading on BBC during my random bursts of surfing.
However, I noted that these failures in resolving (or could be something else) were very odd, happening even after I’d successfully opened a web page. Switching to my former DNS, OpenDNS, makes all the issues go away, making me certain about the fault lying within Google’s service. I’m continuing to use OpenDNS here-on, until a good news article about the other trickles down my feed reader someday.
I leave it to my lurking readers to identify an oddity in the speedometer image used on Google’s DNS page.
I totally agree…
geekyogi
2 Jan 10 at 5:22 pm
Weird, I’m not having any trouble
I hate OpenDNS’s hijacking my 404 pages (atleast that was it was doing last time I checked), so was using 4.4.2.1 and 4.4.2.2
Yuvi
2 Jan 10 at 9:54 pm
You mean non-responsive servers I think? I used to miss it when I relied on Firefox + I’m Feeling Lucky integration, but guess I got over that.
Google’s much quicker at resolving though, about half the rtt of OpenDNS via my ISP – just gets on my nerves at times with certain sites not resolving properly (not updated frequently perhaps).
Harsh
2 Jan 10 at 10:32 pm
Yeah, I still rely on I’m Feeling Lucky integration quite a bit (hope there’s some way to force chrome into that too)
Yuvi
2 Jan 10 at 10:33 pm
Don’t know of a way to force that but a custom search + keyword can do that I think. You’d only have to tweak the btnl search parameter to use the I’m Feeling Lucky option
Harsh
2 Jan 10 at 10:36 pm