Comments on: Test Driving Google Public DNS (Updated with OpenDNS comparison)

By: Andy

Andy — Sat, 05 May 2012 13:11:26 +0000

@Clive – Interesting result, but I wonder if it’s reproducible. If so, it would appear to be a geolocation failure on Speedtest’s part – which is plausible given that, at least where I live, OpenDNS’s servers are closer than Google’s. If other sites then use that same geolocation algorithm, that could have a big impact on your real-world experience, of course.

By: Clive

Clive — Sat, 05 May 2012 11:29:19 +0000

I used Open DNS and used Speedtest.com to check upload and download speeds.With Open DNS download was 1.12MBs. Ping 46ms
With Google DNS Download was a measly 0.22MBs. ping 135ms.
So have gone back to Open DNS.

By: Andy

Andy — Thu, 03 Dec 2009 23:09:38 +0000

@Raj – As query response times – reported by “dig” as “Query time” – fell into two fairly tight groups, it seemed a reasonable assumption to assume the the faster responses were served out of cache, while the slower response times were not. Noting that repeated queries of the same hostname were always faster and always tightly clustered bears this out. You could also look at the TTL of the returned record to see if it is cached or not – if it is below what the authoritative host has for it, you know you’re looking at a cache hit.

By: Raj

Raj — Thu, 03 Dec 2009 22:35:25 +0000

Hey I wnated to know how you compared public dns and opendns .I mean what tool did you use to see the cache hit and miss ratio.I want to test the cache hit and miss of some DNS related app need info and help on that