News for hackers. Stuff that matters.
Re:Google Cloud DNS by jread on Tuesday April 29, 2014 @12:16AM (#7664916)
It's a start - barebones authoritative DNS only - no monitoring/failover, load balancing, Geo, LBR, etc - provisioning via API only. Route 53 started out this way, and has since added many of these features and now has almost 7% Alexa 10k marketshare and rapidly growing.

I created a browser test that measures recursive DNS query times. You can test Google DNS query performance using this link: http://bit.ly/1nY4e60

Re:Google Cloud DNS by biot on Tuesday April 29, 2014 @04:24AM (#7665699)
Please don't post mystery meat URLs. The bit.ly link goes to: http://cloudharmony.com/speedtest/run?services_CDN=&serviceT...
Re:Google Cloud DNS by tfountain on Tuesday April 29, 2014 @06:23AM (#7666023)
Could you provide any more info on how this test works? Where are the tests performed from, or do they run client side? Does it query name servers directly, or if not, how does it avoid ISP-level DNS caching influencing the results?
Re:Google Cloud DNS by jread on Tuesday April 29, 2014 @06:29AM (#7666040)
Tests are from your connection using whatever resolver chain your ISP has in place. It uses a wildcard name record and an 8 byte json-p include. It alternates between downloading that file from the same origin using a cached DNS record (test run up includes 3 downloads to prime the resolvers with a cached hostname) and an uncached record (a new randomly generated hostname) and reports the difference in time between the two.
Re:Google Cloud DNS by nickpresta on Tuesday April 29, 2014 @12:46AM (#7665019)
My results, from Toronto:

http://i.imgur.com/hOayTQH.png