Here at ThousandEyes, we’ve always been curious about the performance of various public DNS resolvers — especially since Google threw their hat in the ring back in 2009. We satisfied our curiosity this week, so we thought we’d share the results.
Here’s how we did it. We measured the latency to each resolver from approximately 3000 points around the globe with a minimum of 50 points per country. This means that these results are based on the best-case resolution time, assuming you tried to retrieve a DNS record that was in the public resolver’s cache. The results shown are the average over a 24-hour period.
Using this data, we determined which DNS provider’s resolvers were fastest (on average) as seen by each of the vantage points. We picked a winner per country based on the provider that was most frequently the fastest in that country. The map below is colored accordingly. As you can see, if you are in the US, chances are that your fastest public resolver is an OpenDNS resolver. But if you’re in India, it’s probably Google.
Global Results:
| Resolver | Avg Latency | % Where Fastest |
|---|---|---|
| Google 1 (8.8.8.8) | 61.1 ms | 20.7% |
| Google 2 (8.8.4.4) | 61.2 ms | 19.0% |
| Dyn 1 (216.146.35.35) | 94.6 ms | 13.5% |
| OpenDNS 2 (208.67.220.220) | 84.6 ms | 11.8% |
| OpenDNS 1 (208.67.222.222) | 85.5 ms | 10.9% |
| Dyn 2 (216.146.36.36) | 95.8 ms | 10.2% |
| Ultra 2 (156.154.71.1) | 105.4 ms | 7.6% |
| Ultra 1 (156.154.70.1) | 117.9 ms | 3.5% |
| Level3 2 (4.2.2.2) | 169.0 ms | 1.7% |
| Level3 1 (4.2.2.1) | 217.7 ms | 1.1% |
United States Results:
| Resolver | Avg Latency | % Where Fastest |
|---|---|---|
| OpenDNS 2 (208.67.220.220) | 18.2 ms | 27.3% |
| OpenDNS 1 (208.67.222.222) | 17.8 ms | 27.2% |
| Dyn 2 (216.146.36.36) | 23.6 ms | 8.7% |
| Ultra 1 (156.154.70.1) | 28.6 ms | 7.8% |
| Dyn 1 (216.146.35.35) | 25.7 ms | 7.7% |
| Ultra 2 (156.154.71.1) | 24.2 ms | 6.7% |
| Level3 1 (4.2.2.1) | 34.6 ms | 5.9% |
| Level3 2 (4.2.2.2) | 28.1 ms | 4.8% |
| Google 2 (8.8.4.4) | 31.2 ms | 2.3% |
| Google 1 (8.8.8.8) | 32.0 ms | 1.6% |
Most regions have a clear frontrunner — OpenDNS in North America, Central America, and Africa, Google in South America and the Asia-Pacific region, and Dyn in eastern Europe. In western Europe, however, there is a bit more contention for the top spot, with each of the top three providers making a strong showing. At a country level, Level3 DNS resolvers did not make it to the top anywhere while Ultra’s DNS resolvers made it to the top in Hong Kong (though you can’t see it on the map).
Now that our initial curiosity about the performance of different public DNS resolvers has been satisfied, our next task is to understand how the performance of public resolvers compares to the default resolver provided by your local ISP. That’s definitely more involved and will be the subject of an upcoming article.










Pingback: Google vencedora en una comparativa mundial de servidores DNS públicos
Pingback: De entre los DNS públicos, los de Google son los más rápidos en España
Pingback: DNS publicos de Google son los más rápidos – Taringa! Buzz
From SF, I get the best ping times to Level3 DNS severs, followed by Open DNS, and lastly Google DNS. traceroute to each one of these also shows the least number to hops to Level3, followed by Open DNS and lastly Google DNS. It seems like Level3 has a DNS in San Jose. Course none are as fast as Comcast’s primary DNS server for the bay area.
Why is it hard to measure ping times to ISP’s DNS. Comcast has its DSN’s publicly listed, and I imagine that others do the same. Is it a matter of having a client within the ISP’s network? Coz short of that the ping times will not accurately reflect an ISP’s customer’s viewpoint.
Pingback: Los servidores DNS de Google son los más rápidos : Geek Pro
Pingback: ¿Qué DNS utilizas? Un estudio asegura que las de Google son las más rápidas - Ofertas ADSL
Pingback: Google's public DNS are the fastest | UYX NOTICES
while doing this can be advantageous to a lot of people if you dont live in USA it can be a real slowdown.
as these public DNS are almost all located in america a lot of sites use a lazy way of determining your location based on where the DNS request came from. This results in you being pointed to the american download servers or content servers and as a result you will have trouble being able to even watch a youtube video if you are somewhere like NZ.
………………
Jack
I didn’t even know that Google introduced its own DNS resolver.
Was using OpenDNS for… almost forever, but just now encountered a problem where OpenDNS got stuck on old IP for one site, switched to Google, after finding this post and got access to it. Well, I’ll give OpenDNS additional day to get it right
If not I might even stay on Google one.