Google Public DNS vs OpenDNS vs Your ISP's DNS - measuring performance

Uncategorized Add comments
Dec 042009

Like many in the industry, we were surprised and intrigued by the announcement yesterday that Google would be entering the DNS business. The basic logic was clear: Google has a vested interest in the internet being fast, and so they want to offer a free public utility to help it be faster.

Of course, some were doubtful. OpenDNS, probably the company that has the most to lose by this decision, responded quickly. Some questioned its security, while others pointed out that Google gains a lot more than you might think by serving DNS: it would now know everywhere you were going, regardless of whether you went through Google Search or whether the site had Google Analytics installed.

While we’re not going to get in to the broader debate of whether this move is Good or Evil, we were curious if their service really offered significant performance benefits. So we extracted the DNS code from our BrowserMob website monitoring service (which itself is based on the fantastic xbill Java DNS library), and built a quick-n-dirty tool to measure exactly that.

The results

Here’s how it works: our tool queries the Alexa worldwide top 1000 sites. It does it against Google Public DNS, OpenDNS, and (optionally) the DNS servers of your choosing. Since we’re located in Portland, OR and have a Qwest internet connection, we used Qwest’s DNS servers in our test. The results surprised us: 

Starting test...
 
Test 1: Google
85109 ms for 1000 records
Test 2: Google
67586 ms for 1000 records
Test 3: Google
67318 ms for 1000 records
Test 1: OpenDNS
92521 ms for 1000 records
Test 2: OpenDNS
45793 ms for 1000 records
Test 3: OpenDNS
47899 ms for 1000 records
Test 1: Your DNS
62541 ms for 1000 records
Test 2: Your DNS
25561 ms for 1000 records
Test 3: Your DNS
25879 ms for 1000 records

Taking the lowest time and dividing by 1000 tells us the average DNS lookup times from our location in Portland, OR:

  • Google – 67.3 ms
  • OpenDNS – 45.8 ms
  • Qwest DNS – 25.6 ms

What this told us was that despite all the hoopla about performance, our trusty old DNS server we’ve always been using is still the fastest. And when you think about it, it shouldn’t be a surprise: there are fewer hops from the computer to the DNS server because it’s the same ISP.

We were very surprised, however, to see how much faster OpenDNS was compared to Google. While both are slower than your local ISP’s, OpenDNS promises a bunch of features which might help make up for the performance difference. While Google isn’t promising any features right now, they are, as always, pledging to not be evil. Considering that some ISPs have in the past redirect DNS lookups to serve their commercial interests, Google’s pledge is worth noting.

Running your own test

These results were from a Qwest DSL connection in Portland, OR. We’re curious what your results are, so we’ve made the test available for everyone. It requires Java and can be run like so:

java -jar browsermob-dns-perf.jar

If you wish to test your ISP’s DNS, just add to the command line one or more IPs: 

java -jar browsermob-dns-perf.jar 123.456.789.012

We hope that you will comment on this blog with the results you get. We’re very curious to see what the worldwide performance results are.

A note about the test

DNS is somewhat hard to test for performance, since there are many moving pieces. The results can depend on whether the server has a cached entry, how far you are from the DNS server, how far the DNS server is from the other servers, etc. This is why we run the test three times for each service an why we think the right approach here is to take the best score.

However, we do understand one could easily argue that the first result is much more critical. We sort of agree, but the problem is that because these are public services you can’t tell how “fresh” the cache is on the servers you are testing against.

In fact, we should note that Google’s FAQ argues that cache misses are big performance issue and the main benefit they bring to the table. Unfortunately, this is extremely difficult, if not impossible, for us to independently test. As such, we decided that the most consistent and useful result would be the faster time for each service, even if that means it was faster due to 100% cache hits.


Posted by Patrick Lightbody at 2:29 pm Tagged with: , ,

198 Responses to “Google Public DNS vs OpenDNS vs Your ISP’s DNS – measuring performance”

  1. Erling says:
    February 10, 2011 at 11:59 am

    From Tórshavn, Faroe Islands – ISP: vodafone.fo

    Test 1: Google
    116253 ms for 1000 records
    Test 2: Google
    80084 ms for 1000 records
    Test 3: Google
    82643 ms for 1000 records
    Test 1: OpenDNS
    263711 ms for 1000 records
    Test 2: OpenDNS
    83620 ms for 1000 records
    Test 3: OpenDNS
    88304 ms for 1000 records
    Test 1: Your DNS
    212312 ms for 1000 records
    Test 2: Your DNS
    30872 ms for 1000 records
    Test 3: Your DNS
    27042 ms for 1000 records

  2. Sten C says:
    February 10, 2011 at 4:01 pm

    Local DNS: 192.168.16.32

    Test 1: Google
    74112 ms for 1000 records
    Test 2: Google
    65168 ms for 1000 records
    Test 3: Google
    65322 ms for 1000 records
    Test 1: OpenDNS
    324965 ms for 1000 records
    Test 2: OpenDNS
    75588 ms for 1000 records
    Test 3: OpenDNS
    71203 ms for 1000 records
    Test 1: Your DNS
    362568 ms for 1000 records
    Test 2: Your DNS
    36982 ms for 1000 records
    Test 3: Your DNS
    12135 ms for 1000 records

    As can be seen this test clearly benefits from caching the answers from test to test.

    Ping time 20ms

    I believe my own DNS is clearly best if I use the same addresses even just a few times.

  3. Ahmad says:
    February 11, 2011 at 11:50 am

    From Saudi Arabia (ADSL STC AFAQ)

    # java -jar browsermob-dns-perf.jar 84.235.6.55 84.235.57.230

    Starting test…

    Test 1: Google
    180958 ms for 1000 records
    Test 2: Google
    128087 ms for 1000 records
    Test 3: Google
    139921 ms for 1000 records
    Test 1: OpenDNS
    277863 ms for 1000 records
    Test 2: OpenDNS
    151294 ms for 1000 records
    Test 3: OpenDNS
    171674 ms for 1000 records
    Test 1: Your DNS
    210186 ms for 1000 records
    Test 2: Your DNS
    193805 ms for 1000 records
    Test 3: Your DNS
    187823 ms for 1000 records

    Use any service except AFAQ DNS !! (my own ISP is the worst!!)

  4. john says:
    February 18, 2011 at 11:55 pm

    it freezes on first line : test 1:google and then nothing happens.

  5. tarja h. says:
    February 20, 2011 at 11:51 am

    My ISP is (ADSL Broadband) Elisa Laajakaista.

    Test 1: Google
    126139 ms for 1000 records
    Test 2: Google
    82962 ms for 1000 records
    Test 3: Google
    78000 ms for 1000 records
    Test 1: OpenDNS
    326415 ms for 1000 records
    Test 2: OpenDNS
    213595 ms for 1000 records
    Test 3: OpenDNS
    250662 ms for 1000 records
    Test 1: Your DNS
    211208 ms for 1000 records
    Test 2: Your DNS
    79139 ms for 1000 records
    Test 3: Your DNS
    61823 ms for 1000 records

  6. Anonymous says:
    March 7, 2011 at 1:21 am

    Test 1: Google
    72387 ms for 1000 records
    Test 2: Google
    47492 ms for 1000 records
    Test 3: Google
    57695 ms for 1000 records
    Test 1: OpenDNS
    48632 ms for 1000 records
    Test 2: OpenDNS
    31718 ms for 1000 records
    Test 3: OpenDNS
    30106 ms for 1000 records
    Test 1: Your DNS
    141337 ms for 1000 records
    Test 2: Your DNS
    129124 ms for 1000 records
    Test 3: Your DNS
    122011 ms for 1000 records
    Through my DD-WRT router with DNSMASQ running, so don’t know if it’s “skewed”. My ISP is Time Warner/Roadrunner in Barstow, their DNS matches the rest of their service. Looks like I’m going with OpenDNS.
    Thanks!

  7. javier says:
    April 12, 2011 at 12:17 pm

    From Chile (ISP VTR)
    $ java -jar browsermob-dns-perf.jar 200.104.255.130 200.74.121.200

    Test 1: Google
    204870 ms for 1000 records
    Test 2: Google
    110723 ms for 1000 records
    Test 3: Google
    114806 ms for 1000 records
    Test 1: OpenDNS
    272432 ms for 1000 records
    Test 2: OpenDNS
    180259 ms for 1000 records
    Test 3: OpenDNS
    204094 ms for 1000 records
    Test 1: Your DNS
    35893 ms for 1000 records
    Test 2: Your DNS
    37585 ms for 1000 records
    Test 3: Your DNS
    39349 ms for 1000 records

    Thanks!

  8. Bruce says:
    May 20, 2011 at 4:17 am

    Cox Cable, Hampton Roads, VA

    I’m going with google dns because of the lower results for the first query.

    Test 1: Google
    79643 ms for 1000 records
    Test 2: Google
    37512 ms for 1000 records
    Test 3: Google
    33198 ms for 1000 records

    Test 1: OpenDNS
    172494 ms for 1000 records
    Test 2: OpenDNS
    27942 ms for 1000 records
    Test 3: OpenDNS
    21593 ms for 1000 records

    Test 1: Your DNS
    156249 ms for 1000 records
    Test 2: Your DNS
    139693 ms for 1000 records
    Test 3: Your DNS
    134710 ms for 1000 records

  9. Yaakov says:
    May 30, 2011 at 3:47 am

    My ISP = Netvision, Israel

    Test 1: Google
    195888 ms for 1000 records
    Test 2: Google
    121908 ms for 1000 records
    Test 3: Google
    131670 ms for 1000 records

    Test 1: OpenDNS
    324297 ms for 1000 records
    Test 2: OpenDNS
    161395 ms for 1000 records
    Test 3: OpenDNS
    158344 ms for 1000 records

    Test 1: Your DNS
    55960 ms for 1000 records
    Test 2: Your DNS
    51027 ms for 1000 records
    Test 3: Your DNS
    50837 ms for 1000 records

    Thank you!

  10. Watcher says:
    June 8, 2011 at 7:41 am

    While it’s true that external DNS services such as GNDS and ODNS do tend to take longer at resolution, they tend to be far more RELIABLE than the ISP DNS servers.

    Personally, I do not use my ISP dns servers. I prefer to use ODNS. When our local ISP is having dns issues, I still have site access while 1/2 of my neighborhood doesn’t have access at all.

    So to me, it’s wise to also comment that reliability is also a HUGE factor in which to chose.

  11. Emerson Prado says:
    June 15, 2011 at 9:07 am

    Test 1: Google
    168604 ms for 1000 records
    Test 2: Google
    35314 ms for 1000 records
    Test 3: Google
    25350 ms for 1000 records
    Test 1: OpenDNS
    300491 ms for 1000 records
    Test 2: OpenDNS
    149678 ms for 1000 records
    Test 3: OpenDNS
    167160 ms for 1000 records
    Test 1: Your DNS
    342161 ms for 1000 records
    Test 2: Your DNS
    58650 ms for 1000 records
    Test 3: Your DNS
    48368 ms for 1000 records

    A good tool called namebench does a more complete testing, with max/min/avg times and so on, using lots of DNS servers. With that, I found out that Google and a couple ISPs provide better DNSs than my own.
    But manual configuration must always provide an internal DNS (router, internet server…, whoever answers to 192.168.1.1) when there’s one.
    Best regards,
    Emerson

  12. Crashthatch says:
    June 28, 2011 at 4:36 am

    Virgin ISP, from Bath, UK, 194.168.4.100:

    Test 1: Google
    106962 ms for 1000 records
    Test 2: Google
    45053 ms for 1000 records
    Test 3: Google
    42903 ms for 1000 records
    Test 1: OpenDNS
    231406 ms for 1000 records
    Test 2: OpenDNS
    47325 ms for 1000 records
    Test 3: OpenDNS
    38576 ms for 1000 records
    Test 1: Your DNS
    168048 ms for 1000 records
    Test 2: Your DNS
    29853 ms for 1000 records
    Test 3: Your DNS
    12360 ms for 1000 records

  13. SouthernCross says:
    July 11, 2011 at 5:50 pm

    For those of us who are not real network savvy…

    You state in your utility,

    “Please make sure you are using DNS servers that aren’t simple relays to another serivce, such as your wireless router…”

    I’m on a Windows machine and entered “ipconfig /all” in cmd.exe. I then used the IP address under the “Ethernet adapter Local Area Connection –> DNS Servers” entry.

    Is this a reasonable way to determine the correct IP to use for my ISP’s DNS? Seems to me that it would be, but, again, I’m not a networking guy…

    Thx in advance.

  14. SouthernCross says:
    July 11, 2011 at 6:42 pm

    Here are my results using 208.67.222.123 (myhome.westell.com):

    Test 1: Google
    116437 ms for 1000 records
    Test 2: Google
    102003 ms for 1000 records
    Test 3: Google
    70749 ms for 1000 records
    Test 1: OpenDNS
    202926 ms for 1000 records
    Test 2: OpenDNS
    89439 ms for 1000 records
    Test 3: OpenDNS
    72540 ms for 1000 records
    Test 1: Your DNS
    180135 ms for 1000 records
    Test 2: Your DNS
    104465 ms for 1000 records
    Test 3: Your DNS
    93876 ms for 1000 records

  15. SanS says:
    July 15, 2011 at 2:59 pm

    Test from Chantilly, VA. IS: Verizon FiOS.

    Starting test…

    Test 1: Google
    93110 ms for 1000 records
    Test 2: Google
    84421 ms for 1000 records
    Test 3: Google
    72563 ms for 1000 records
    Test 1: OpenDNS
    95375 ms for 1000 records
    Test 2: OpenDNS
    43328 ms for 1000 records
    Test 3: OpenDNS
    32516 ms for 1000 records
    Test 1: Your DNS
    159390 ms for 1000 records
    Test 2: Your DNS
    115344 ms for 1000 records
    Test 3: Your DNS
    99734 ms for 1000 records

  16. Amaimon says:
    July 31, 2011 at 2:30 pm

    From Hosting.com Irvine, CA

    Starting test…

    Test 1: Google
    164087 ms for 1000 records
    Test 2: Google
    119491 ms for 1000 records
    Test 3: Google
    117028 ms for 1000 records

    Test 1: OpenDNS
    118055 ms for 1000 records
    Test 2: OpenDNS
    10545 ms for 1000 records
    Test 3: OpenDNS
    6973 ms for 1000 records

    Test 1: Your DNS
    209636 ms for 1000 records
    Test 2: Your DNS
    19533 ms for 1000 records
    Test 3: Your DNS
    14337 ms for 1000 records

  17. ighem says:
    August 15, 2011 at 12:01 pm

    pengen belajar lbi dalam lgi tentang ”The BrowserMob Blog”

  18. Casemon says:
    August 19, 2011 at 9:21 am

    Starting test…

    Test 1: Google
    60857 ms for 1000 records
    Test 2: Google
    62885 ms for 1000 records
    Test 3: Google
    69951 ms for 1000 records
    Test 1: OpenDNS
    137840 ms for 1000 records
    Test 2: OpenDNS
    51432 ms for 1000 records
    Test 3: OpenDNS
    42185 ms for 1000 records
    Test 1: Your DNS
    112066 ms for 1000 records
    Test 2: Your DNS
    91759 ms for 1000 records
    Test 3: Your DNS
    89901 ms for 1000 records

  19. Heroes says:
    August 23, 2011 at 6:20 pm

    Test, From Vitry Sur Seine, FRANCE (ram94-5-82-229-223-211.fbx.proxad.net [82.229.223.211])

    Starting test…

    Test 1: Google
    3422 ms for 1000 records
    Test 2: Google
    3228 ms for 1000 records
    Test 3: Google
    3181 ms for 1000 records
    Test 1: OpenDNS
    3175 ms for 1000 records
    Test 2: OpenDNS
    3170 ms for 1000 records
    Test 3: OpenDNS
    3164 ms for 1000 records
    Test 1: Your DNS
    1386 ms for 1000 records
    Test 2: Your DNS
    1360 ms for 1000 records
    Test 3: Your DNS
    1357 ms for 1000 records

    C:\Users\Benj>

  20. Heroes says:
    August 23, 2011 at 6:24 pm

    If you don’t believe the result a little screen.

    http://www.hostpic.org/images/81Sans_titre.png

  21. Chuck Yoder says:
    August 30, 2011 at 10:02 am

    Time Warner, North East Ohio

    Starting test…

    Test 1: Google
    75724 ms for 1000 records
    Test 2: Google
    52010 ms for 1000 records
    Test 3: Google
    49874 ms for 1000 records
    Test 1: OpenDNS
    99700 ms for 1000 records
    Test 2: OpenDNS
    61152 ms for 1000 records
    Test 3: OpenDNS
    68141 ms for 1000 records
    Test 1: Your DNS
    132663 ms for 1000 records
    Test 2: Your DNS
    127343 ms for 1000 records
    Test 3: Your DNS
    105643 ms for 1000 records

  22. Duffy says:
    August 31, 2011 at 7:41 am

    Nusa Dua, Bali, Indonesia
    (SmartFren 3G modem attached directly to PC and no other web apps running).

    Google seems to have taken the lead for me as well.

    Starting test…

    Test 1: Google
    278078 ms for 1000 records
    Test 2: Google
    186935 ms for 1000 records
    Test 3: Google
    194963 ms for 1000 records
    Test 1: OpenDNS
    402572 ms for 1000 records
    Test 2: OpenDNS
    243081 ms for 1000 records
    Test 3: OpenDNS
    245599 ms for 1000 records
    Test 1: Your DNS
    412279 ms for 1000 records
    Test 2: Your DNS
    320685 ms for 1000 records
    Test 3: Your DNS
    308683 ms for 1000 records

    Thanks again!

  23. DNS says:
    September 10, 2011 at 9:41 pm

    Verizon High Speed Internet DSL

    Starting test…

    Test 1: Google
    196385 ms for 1000 records
    Test 2: Google
    179211 ms for 1000 records
    Test 3: Google
    166318 ms for 1000 records
    Test 1: OpenDNS
    124010 ms for 1000 records
    Test 2: OpenDNS
    65281 ms for 1000 records
    Test 3: OpenDNS
    64471 ms for 1000 records
    Test 1: Your DNS
    113056 ms for 1000 records
    Test 2: Your DNS
    102735 ms for 1000 records
    Test 3: Your DNS
    93036 ms for 1000 records

  24. James Long says:
    September 21, 2011 at 2:12 pm

    Viaero Wireless

    Test 1: Google
    789454 ms for 1000 records
    Test 2: Google
    705937 ms for 1000 records
    Test 3: Google
    764890 ms for 1000 records
    Test 1: OpenDNS
    831641 ms for 1000 records
    Test 2: OpenDNS
    694609 ms for 1000 records
    Test 3: OpenDNS
    659172 ms for 1000 records
    Test 1: Your DNS
    848781 ms for 1000 records
    Test 2: Your DNS
    976860 ms for 1000 records
    Test 3: Your DNS
    198140 ms for 1000 records

    Um.. Can anyone explain why the last DNS test went WAY faster??

    I still don’t quite understand why we’re not averaging out the DNS response times. I kinda thought that that was the golden rule. Anyway, I’m not at all convinced that the final result is accurate. If anyone is interested, I’ll run another series late at night.

    Finally, what in the name of god does this have to do with Google and OpenDNS redirecting to ‘locally’ cached resources to speed things up??

  25. Darryl says:
    October 14, 2011 at 6:06 am

    ATT Uverse in San Diego (68.94.156.1):

    Test 1: Google
    100586 ms for 1000 records
    Test 2: Google
    65233 ms for 1000 records
    Test 3: Google
    67019 ms for 1000 records

    Test 1: OpenDNS
    96835 ms for 1000 records
    Test 2: OpenDNS
    38630 ms for 1000 records
    Test 3: OpenDNS
    37032 ms for 1000 records

    Test 1: Your DNS
    129417 ms for 1000 records
    Test 2: Your DNS
    113966 ms for 1000 records
    Test 3: Your DNS
    102554 ms for 1000 records

    Looks like OpenDNS is the winner for me. thanks for the script. very helpful.

  26. Ben says:
    October 16, 2011 at 8:53 pm

    Comcast in Northeast Massachusetts.

    Starting test…

    Test 1: Google
    60600 ms for 1000 records
    Test 2: Google
    29327 ms for 1000 records
    Test 3: Google
    29574 ms for 1000 records
    Test 1: OpenDNS
    149582 ms for 1000 records
    Test 2: OpenDNS
    25871 ms for 1000 records
    Test 3: OpenDNS
    22687 ms for 1000 records
    Test 1: Your DNS
    96979 ms for 1000 records
    Test 2: Your DNS
    81227 ms for 1000 records
    Test 3: Your DNS
    66136 ms for 1000 records

  27. anon says:
    October 22, 2011 at 9:24 am

    Verizon FIOS – Leesburg, VA
    Test 1: Google
    43577 ms for 1000 records
    Test 2: Google
    29593 ms for 1000 records
    Test 3: Google
    31536 ms for 1000 records
    Test 1: OpenDNS
    178440 ms for 1000 records
    Test 2: OpenDNS
    20438 ms for 1000 records
    Test 3: OpenDNS
    13030 ms for 1000 records
    Test 1: Your DNS
    112596 ms for 1000 records
    Test 2: Your DNS
    86092 ms for 1000 records
    Test 3: Your DNS
    62978 ms for 1000 records

  28. spookyfox says:
    October 25, 2011 at 6:53 am

    I have no clue how to test it on my own. What do I do with that java -jar browsermob-dns-perf.jar thing? Where do I put it?

  29. netmasterjohn says:
    October 28, 2011 at 9:32 am

    Looks like I’m out of luck either way. Google, OpenDNS and my local ISP (142.177.2.130) all suck.

    Test 1: Google
    172156 ms for 1000 records
    Test 2: Google
    177217 ms for 1000 records
    Test 3: Google
    178952 ms for 1000 records

    Test 1: OpenDNS
    197623 ms for 1000 records
    Test 2: OpenDNS
    177709 ms for 1000 records
    Test 3: OpenDNS
    178243 ms for 1000 records

    Test 1: Your DNS
    171445 ms for 1000 records
    Test 2: Your DNS
    187013 ms for 1000 records
    Test 3: Your DNS
    169765 ms for 1000 records

  30. Captain Picard says:
    November 17, 2011 at 11:52 am

    Time Warner Cable/Roadrunner – Austin, TX

    Test 1: Google
    83696 ms for 1000 records
    Test 2: Google
    45250 ms for 1000 records
    Test 3: Google
    43199 ms for 1000 records

    Test 1: OpenDNS
    147876 ms for 1000 records
    Test 2: OpenDNS
    47244 ms for 1000 records
    Test 3: OpenDNS
    41584 ms for 1000 records

    Test 1: Your DNS
    128649 ms for 1000 records
    Test 2: Your DNS
    114582 ms for 1000 records
    Test 3: Your DNS
    121325 ms for 1000 records

    Surprising results, I’ve been using OpenDNS for the past few years. Looks like its time to try out the Google servers for a while.

  31. John Langstaff says:
    November 25, 2011 at 9:24 am

    Test 1: Google
    95395 ms for 1000 records
    Test 2: Google
    50232 ms for 1000 records
    Test 3: Google
    57371 ms for 1000 records
    Test 1: OpenDNS
    151507 ms for 1000 records
    Test 2: OpenDNS
    18549 ms for 1000 records
    Test 3: OpenDNS
    33898 ms for 1000 records
    Test 1: Your DNS
    101759 ms for 1000 records
    Test 2: Your DNS
    111072 ms for 1000 records
    Test 3: Your DNS
    100948 ms for 1000 records

  32. John Langstaff says:
    November 25, 2011 at 4:09 pm

    My test results are posted above. ISP is Comcast.

    Comcast’s DNS servers don’t respond to Pings at regular intervals. I questioned Comcast Tier II tech support about that, and they quickly reply that their DNS servers behave like this because of Denial of Service Attack protection. I suspect their test results would suffer as well.

  33. Keith Brister says:
    November 26, 2011 at 1:21 pm

    Chicagoland comcast:

    Test 1: Google
    64031 ms for 1000 records
    Test 2: Google
    44775 ms for 1000 records
    Test 3: Google
    47111 ms for 1000 records

    Test 1: OpenDNS
    135649 ms for 1000 records
    Test 2: OpenDNS
    66843 ms for 1000 records
    Test 3: OpenDNS
    66993 ms for 1000 records

    Test 1: Your DNS
    156499 ms for 1000 records
    Test 2: Your DNS
    137883 ms for 1000 records
    Test 3: Your DNS
    118553 ms for 1000 records

    Google: 44.8 msec
    OpenDNS: 66.8 msec
    Comcast: 118.6 msec

    Thanks for the “quick-n-dirty tool”!

  34. Aaron C. says:
    December 9, 2011 at 9:19 pm

    Local ISP is Truvista Communications in SC.

    Suprprisingly, google beat all, INCLUDING my local ISP. To top it, I’ve been seeing a lot of recent reliability issues with my ISP’s DNS servers…. I might just be switching…

    Test 1: Google
    90745 ms for 1000 records
    Test 2: Google
    31588 ms for 1000 records
    Test 3: Google
    31712 ms for 1000 records
    Test 1: OpenDNS
    254482 ms for 1000 records
    Test 2: OpenDNS
    48651 ms for 1000 records
    Test 3: OpenDNS
    46840 ms for 1000 records
    Test 1: Your DNS
    296114 ms for 1000 records
    Test 2: Your DNS
    35684 ms for 1000 records
    Test 3: Your DNS
    303917 ms for 1000 records

  35. Vitor Mangraviti says:
    December 12, 2011 at 9:36 am

    If a DNS server takes an extra one fifth of a second looking up, that doesn’t make any difference at all between them all.

    I use Virgin Media in the UK but because my government is always blocking sites and spying on internet users, I rather use something else (along with proxies, VPN’s and all the stuff required to be anonimous on the web).

    Starting with OpenDNS, I was very happy with the service untill I hit a wall: Linux Samba X Windows shares. Simply doesn’t work. That is because OpenDNS has a security feature that blocks unresolvable names.

    As I couldn’t be bothered to sort out the problem with OpenDNS, I am now using Google DNS – which is not the fastest resolving service but a tenth of a second is nothing to me.

    I decided using a free DNS at the moment I tried to access “The Pirate Bay” and my DNS was blocking the site. From then on, I moved on to free DNS and other free services in order to have my privacy intact.

  36. TexasTrader says:
    December 19, 2011 at 2:18 pm

    Open DNS by far faster than Goolge!

    Test 1: Google
    63031 ms for 1000 records
    Test 2: Google
    68359 ms for 1000 records
    Test 3: Google
    64954 ms for 1000 records
    Test 1: OpenDNS
    14390 ms for 1000 records
    Test 2: OpenDNS
    15531 ms for 1000 records
    Test 3: OpenDNS
    13891 ms for 1000 records
    Exception in thread “main” java.net.UnknownHostException: 123.456.789.012
    at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method)
    at java.net.InetAddress$1.lookupAllHostAddr(Unknown Source)
    at java.net.InetAddress.getAddressFromNameService(Unknown Source)
    at java.net.InetAddress.getAllByName0(Unknown Source)
    at java.net.InetAddress.getAllByName(Unknown Source)
    at java.net.InetAddress.getAllByName(Unknown Source)
    at java.net.InetAddress.getByName(Unknown Source)
    at org.xbill.DNS.SimpleResolver.(SimpleResolver.java:59)
    at org.xbill.DNS.ExtendedResolver.(ExtendedResolver.java:283)
    at com.browsermob.dnsperf.Main.testSet(Main.java:50)
    at com.browsermob.dnsperf.Main.main(Main.java:45)

    C:\TOOLS-UTILITIES\DNS_Utilities\DNS_Speedtests>ping 192.168.1.1

  37. not2much4u says:
    January 1, 2012 at 1:27 pm

    Starting test…

    Test 1: Google
    119547 ms for 1000 records
    Test 2: Google
    88390 ms for 1000 records
    Test 3: Google
    103662 ms for 1000 records
    Test 1: OpenDNS
    158590 ms for 1000 records
    Test 2: OpenDNS
    79544 ms for 1000 records
    Test 3: OpenDNS
    80013 ms for 1000 records
    Test 1: Your DNS
    106048 ms for 1000 records
    Test 2: Your DNS
    45489 ms for 1000 records
    Test 3: Your DNS
    66784 ms for 1000 records

  38. Anfy says:
    January 5, 2012 at 1:49 pm

    java -jar browsermob-dns-perf.jar 195.54.122.200 (BBB Swe)

    Test 1: Google
    114766 ms for 1000 records
    Test 2: Google
    49158 ms for 1000 records
    Test 3: Google
    43064 ms for 1000 records
    Test 1: OpenDNS
    202836 ms for 1000 records
    Test 2: OpenDNS
    59557 ms for 1000 records
    Test 3: OpenDNS
    34159 ms for 1000 records
    Test 1: Your DNS
    166599 ms for 1000 records
    Test 2: Your DNS
    21057 ms for 1000 records
    Test 3: Your DNS
    15511 ms for 1000 records

  39. Kevin says:
    January 7, 2012 at 4:28 pm

    Time Warner Cable – Brooklyn, NY (209.18.47.61)

    Test 1: Google
    45049 ms for 1000 records
    Test 2: Google
    40444 ms for 1000 records
    Test 3: Google
    47059 ms for 1000 records
    Test 1: OpenDNS
    202762 ms for 1000 records
    Test 2: OpenDNS
    69420 ms for 1000 records
    Test 3: OpenDNS
    68354 ms for 1000 records
    Test 1: Your DNS
    119396 ms for 1000 records
    Test 2: Your DNS
    133853 ms for 1000 records
    Test 3: Your DNS
    124729 ms for 1000 records

  40. Tom Roberts says:
    January 20, 2012 at 3:48 pm

    “Taking the lowest time and dividing by 1000 tells us the average DNS lookup times from our location in Portland, OR”

    Actually this tells us the minimum DNS lookup times. If you want the average you need to add all three of the tests and divide by 3000. This gives:

    Google: 73.3ms
    OpenDNS: 62.1ms
    QwestDNS: 38.0ms

  41. Marcelo Maciel says:
    January 25, 2012 at 9:32 am

    NET Virtua Belo Horizonte MG Brasil – 201.17.128.103

    Test 1: Google
    145657 ms for 1000 records
    Test 2: Google
    160539 ms for 1000 records
    Test 3: Google
    191882 ms for 1000 records
    Test 1: OpenDNS
    206190 ms for 1000 records
    Test 2: OpenDNS
    186036 ms for 1000 records
    Test 3: OpenDNS
    361860 ms for 1000 records
    Test 1: Your DNS
    281969 ms for 1000 records
    Test 2: Your DNS
    44509 ms for 1000 records
    Test 3: Your DNS
    51130 ms for 1000 records

    My ISP DNS is faster, but the first test was terrible. I will continue using Open DNS for the filters I can you in my house.

  42. Stefan says:
    January 29, 2012 at 9:56 pm

    Location: Switzerland
    Provider: Cablecom 20 Mbit/s

    Test 1: Google
    88838 ms for 1000 records
    Test 2: Google
    35237 ms for 1000 records
    Test 3: Google
    33747 ms for 1000 records
    Test 1: OpenDNS
    185065 ms for 1000 records
    Test 2: OpenDNS
    81455 ms for 1000 records
    Test 3: OpenDNS
    94777 ms for 1000 records
    Test 1: Your DNS
    163681 ms for 1000 records
    Test 2: Your DNS
    105221 ms for 1000 records
    Test 3: Your DNS
    69752 ms for 1000 records

  43. Shawn Kimble says:
    February 7, 2012 at 7:39 am

    Hargray.com 64.203.254.30 – HHI, SC 29928

    Starting test…

    Test 1: Google
    125344 ms for 1000 records
    Test 2: Google
    75406 ms for 1000 records
    Test 3: Google
    73172 ms for 1000 records
    Test 1: OpenDNS
    170625 ms for 1000 records
    Test 2: OpenDNS
    44609 ms for 1000 records
    Test 3: OpenDNS
    43844 ms for 1000 records
    Test 1: Your DNS
    349422 ms for 1000 records
    Test 2: Your DNS
    57531 ms for 1000 records
    Test 3: Your DNS
    36547 ms for 1000 records

    Horrible

  44. Harrob says:
    February 13, 2012 at 7:02 am

    Test 1: Google
    143797 ms for 1000 records
    Test 2: Google
    102375 ms for 1000 records
    Test 3: Google
    100904 ms for 1000 records
    Test 1: OpenDNS
    239363 ms for 1000 records
    Test 2: OpenDNS
    161362 ms for 1000 records
    Test 3: OpenDNS
    184762 ms for 1000 records
    Test 1: Hansenet (Alice) ISP
    166271 ms for 1000 records
    Test 2: 85.214.20.141 (FoeBud)
    63945 ms for 1000 records
    Test 3: 213.73.91.35 (dnscache.berlin.ccc.de)
    46094 ms for 1000 records

  45. Harrob says:
    February 13, 2012 at 7:03 am

    Location: Munich, Germany

    Test 1: Google
    143797 ms for 1000 records
    Test 2: Google
    102375 ms for 1000 records
    Test 3: Google
    100904 ms for 1000 records
    Test 1: OpenDNS
    239363 ms for 1000 records
    Test 2: OpenDNS
    161362 ms for 1000 records
    Test 3: OpenDNS
    184762 ms for 1000 records
    Test 1: Hansenet (Alice) ISP
    166271 ms for 1000 records
    Test 2: 85.214.20.141 (FoeBud)
    63945 ms for 1000 records
    Test 3: 213.73.91.35 (dnscache.berlin.ccc.de)
    46094 ms for 1000 records

  46. Warren says:
    February 13, 2012 at 3:40 pm

    Clear winner here!!

    The setup: ISP is Cox Cable Phoenix, Airlink101 AR-670W router running DD-WRT with wireless ‘g’ connection, Cisco DPC3010 modem.

    Test run against Google, OpenDNS, Cox Phoenix, and Verizon’s open DNS server. Best of first 3 tests is shown for each.

    Test 2: Google
    89801 ms for 1000 records

    Test 3: OpenDNS
    95126 ms for 1000 records

    Test 2: Your DNS (Cox Phoenix)
    100529 ms for 1000 records

    Test 3: Your DNS (Verizon)
    49391 ms for 1000 records

    I had been using the free Verizon servers (4.2.2.1 through 4.2.2.6) because they don’t show advertising pages on misses – just real 404 error codes. Your test shows them fastest, too. Guess I’ll keep using the Verizon servers!!

  47. Niels Krijger says:
    February 17, 2012 at 1:10 pm

    In The Netherlands:

    Google
    1) 168737
    2) 166575
    3) 161270
    Avg: 165,5ms

    OpenDNS
    1) 309191
    2) 161337
    3) 165645
    Avg: 212,1ms

    Own (T-Mobile Online)
    1) 232931
    2) 124627
    3) 150299
    Avg: 169,2ms

  48. Joseph Ting says:
    February 22, 2012 at 6:03 am

    Malaysia (TM UniFi)

    Test 1: Google
    75493 ms for 1000 records
    Test 2: Google
    24964 ms for 1000 records
    Test 3: Google
    22841 ms for 1000 records
    Test 1: OpenDNS
    306656 ms for 1000 records
    Test 2: OpenDNS
    112871 ms for 1000 records
    Test 3: OpenDNS
    104150 ms for 1000 records
    Test 1: Your DNS (Malaysia TM-UniFi)
    1326811 ms for 1000 records
    Test 2: Your DNS (Malaysia TM-UniFi)
    1301675 ms for 1000 records
    Test 3: Your DNS (Malaysia TM-UniFi)
    1415278 ms for 1000 records

« Older Comments

Leave a Reply

(required)

(required)

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre lang="" line="" escaped="">

 

© 2012 The BrowserMob Blog Suffusion theme by Sayontan Sinha