Hacker News Reader

Comment by cleanbrowsing | Hacker News Reader

Pushed a shell script to compare all of them from your location:

https://github.com/cleanbrowsing/dnsperftest

  $ sh ./dnstest.sh |sort -k 22 -n test10  Average 1.30 2.00 3.90 12.50 18.10 19.70 22.20 27.20 188.10 201.20

View on HN

From Perth, Western Australia:

                  test1   test2   test3   test4   test5   test6   test7   test8   test9   test10  Average 85.80 99.80 105.00 112.60 134.10 136.70 166.40 172.40 194.80 226.50 291.80 481.20

Are you using Telstra by chance? They have the worst routing I've ever seen. I've had huge problems getting good routes for their customers. I've had better luck with "IInet" customers.

I would be curious to see what the ping ms is for status.neocities.org, ideally it's coming from Sydney and not the states.

Not sure, actually! I'm just staying with someone at the moment. They're coincidentally changing broadband provider to this tomorrow - https://node1.com.au/

Thanks.

Paris, France (OVH ADSL link FWIW):

    test1   test2   test3   test4   test5   test6   test7   test8   test9   test10  Average 9.10 9.30 14.50 16.30 17.90 18.20 20.20 22.40 25.20 26.30 61.90 81.60 than all the others.

Singapore, work:
                 test1   test2   test3   test4   test5   test6   test7   test8   test9   test10  Average 2.50 2.80 2.80 2.90 3.10 4.10 22.90 48.30 177.20 186.10 241.70 263.00

Made a couple of changes to add median value and local DNS (via ViewQuest).
  ./dnstest.sh| column -s\, -t Median 3 ms    3.10 ms    3 ms 3 ms    3.00 ms    3 ms 4 ms    3.30 ms    3 ms 2 ms    22.50 ms   2 ms 4 ms    3.30 ms    3 ms 2 ms    31.00 ms   2 ms 3 ms    3.10 ms    3 ms 177 ms  177.90 ms  178 ms 215 ms  258.50 ms  281 ms 186 ms  186.00 ms  186 ms 3 ms    2.80 ms    3 ms 262 ms  266.80 ms  264 ms 0 ms    1.00 ms    0 ms

For DNS performance the average is probably not the correct measurement stick. It's vulnerable to sudden spikes or timeouts which happen a lot in UDP traffic.I recommend measuring the median and p0.5, p99.5 and maybe p99.99 values with a lot of data points. That eliminates any packet issues and laves you with the performance you can expect for 50%, 0.5%, 99.5% and 99.99% of your DNS traffic.

Buenos Aires [City], Argentina
                      test1   test2   test3   test4   test5   test6   test7   test8   test9   test10  Average 1000 ms   610.10 31.90 25.00 30.60 158.80 105.30 160.30 46.00 289.00 290.00 158.30 166.10

thanks for the script, I added my isp (spectrum) and my own server (localbind)Central Ohio
                    test1   test2   test3   test4   test5   test6   test7   test8   test9   test10  Average 1.00 33.80 33.90 34.20 37.10 37.20 39.30 40.20 41.40 57.00 89.20 159.50 162.20

Welp glad to know I was trying to dig www.pornhub.com on my work network.

Good point. Removed it from the default tested domains.

Glad I pulled after it was removed. In some countries (incl. Singapore) this domain is banned & blocked. Plus off-course I ran it from work...

Worse than that, you were running scripts without knowing what they do

To be fair, every single time I install an emacs or vim plugin, npm lib, ruby gem, pip package, or anything close, so do I.Really the only code I audit is a 2 page script on HN because I feel someone might judge me if I don't. But even then, I sort of gave up after the first page.
Computer security is so fubar, it's not even funny.

I used to teach people not to pipe curl to bash.  Now I just add sudo -n tests to my scripts and see if they have passwordless sudo.  It turns out, a lot of people have passwordless sudo.

I'm seeing much closer results:
    cloudflare     32 ms   33 ms   34 ms   39 ms   36 ms   35 ms   29 ms   57 ms   48 ms   33 ms     37.60 42.10 45.40 50.30 30.90 44.40 232.40 104.30 42.30 51.80

Run it with "sort -k 22 -n" to to get it listed in order of performance:*norton is faster for you:
    norton         35 ms   33 ms   33 ms   31 ms   39 ms   34 ms   22 ms   25 ms   24 ms   33 ms     30.90 37.60 42.10 42.30 44.40 45.40 50.30 51.80 104.30 232.40

I had my own script. CloudFlare and CleanBrowsing are great, but my ISP (Telekom) still wins.
  Tested 20 domains 5 times each ">Berlin, Vodafone Kabel Deutschland (Cable):
                 test1   test2   test3   test4   test5   test6   test7   test8   test9   test10  Average 12.30 16.40 20.20 20.70 21.70 23.90 25.50 27.50 29.30 36.20 45.80 62.20
I added Charter (71.10.216.1) to the list, and in Mid-michigan via Charter, they consistently come out ahead by a clear margin for me:
  charter        15 ms   15 ms   15 ms   16 ms   15 ms   15 ms   15 ms   15 ms   15 ms   30 ms     16.60 24.50 25.90 30.60 37.30 38.40 38.70 39.80 66.10 128.30 157.70 all of the runs I've done. Occasionally Google mixes it up for the #2 spot as well, but Neustar, Norton, and Cloudflare just edge them out most of the time.
From New Delhi(Airtel), India
                 test1   test2   test3   test4   test5   test6   test7   test8   test9   test10  Average 37.30 40.80 153.10 106.10 292.60 78.80 59.80 315.80 311.10 358.00 162.50 276.60
From Mumbai, India:
                   test1   test2   test3   test4   test5   test6   test7   test8   test9   test10  Average 15.10 2.60 82.90 20.00 129.20 58.00 4.00 227.80 139.80 205.50 235.90 133.10
Fredericton, Canada:
               test1   test2   test3   test4   test5   test6   test7   test8   test9   test10  Average 37.40 37.50 37.90 38.10 39.20 42.20 45.80 84.80 85.10 118.50 146.10 167.50
London, with BT fibre
                 test1   test2   test3   test4   test5   test6   test7   test8   test9   test10  Average 3.70 3.90 4.00 5.10 5.90 6.70 6.90 8.10 11.80 51.30 63.30 71.70
Italy, TIM:
                 test1   test2   test3   test4   test5   test6   test7   test8   test9   test10  Average 21.10 22.30 29.00 38.70 40.80 42.20 44.70 47.70 56.40 57.60 73.30 91.00
Amsterdam:
  test1   test2   test3   test4   test5   test6   test7   test8   test9   test10  Average 27.10 28.60 37.40 27.20 32.80 65.10 50.40 29.50 57.00 32.80 29.00 37.00
Oddly, I also got the best performance from Norton. An MTR shows Norton at 5 hops, Google at 8 hops and Cloudflare at 7. I might even accept slower speeds for added privacy, luckily I don't have to.
               test1   test2   test3   test4   test5   test6   test7   test8   test9   test10  Average 5.50 5.80 7.00 17.50 20.60 20.90 33.70 46.20 150.60 155.00
What ISP/city you tested it from?
Thanks, this is a very useful script. I added my pi-hole (using neustar as upstream) to the script and found it adds about 2ms to the initial queries. After I ran the script a second time, the pi-hole average was half of neustar, so pi-hole must do some amount of caching.
                 test1   test2   test3   test4   test5   test6   test7   test8   test9   test10  Average 8.90 13.30 13.40 15.10 15.90 16.10 18.80 42.10 44.80 97.50 159.30 174.80
From Oakland on Comcast:
  $ sh ./dnstest.sh | sort -k 22 -n test10  Average 40.60 41.00 41.60 41.80 42.10 42.50 42.90 64.80 81.90 283.00
Comcast in Mountain View, CA.
                   test1   test2   test3   test4   test5   test6   test7   test8   test9   test10  Average 39.10 39.70 40.50 41.10 41.40 42.30 42.40 50.00 80.50 195.30
Something isn't right with those results. Since the lowest average is above 20ms, can you share the results of a traceroute to 1.1.1.1 or 8.8.8.8 or any of the DNS servers in the list?It looks like your results are skewed due to your local network. (On laggy WiFi perhaps?)
I see great differences in the top 5 fastest dns-servers on my Macbook, when running the script a couple of times with like a few minutes in between; everyone posts here are pretty useless i believe (since it's just a single test.)
When using WPT to benchmark network latency from a given location, a rule of thumb I adopted during my years as a webperf engineer was to repeat the test 9x. Using an odd number ensured the median run was an actual test, and 9 seemed sufficient to iron out the inevitable temporal inconsistencies, while allowing the overall test suite to finish in a reasonable time. The fastest value was sometimes more interesting / useful than the median though.
from interior BC:
  % bash ./dnstest.sh test10  Average 29.00 47.50 42.00 40.40 36.30 61.40 78.50 87.40 243.00 89.10 78.30 800.30
Warsaw, Poland
               test1   test2   test3   test4   test5   test6   test7   test8   test9   test10  Average
 15.40 15.30 30.80 28.10 123.10 43.80 41.60 36.10 90.90 54.50 41.50 52.80
The performance is depending on how many concurrent user are using their service.
This is cool; thanks for the script.
Results for Reno, NV on AT&T:Round One:
                   test1   test2   test3   test4   test5   test6   test7   test8   test9   test10  Average 4.00 8.00 8.00 8.00 8.60 17.60 19.40 19.70 27.40 27.60 155.90 192.30 test7   test8   test9   test10  Average 8.00 8.10 8.80 11.30 11.90 13.60 15.90 19.50 19.70 27.40 157.00 188.70 and Cloudflare seem to be consistently fast (~ 8ms averages), while Google and Quad9 are inconsistently fast.  Comodo, Clean Browsing, and OpenDNS are consistently decent, while AdGuard and Yandex are consistently slow.Unrelated note: Clean Browsing looks pretty neat, though I'm curious about how it manages to enforce any kind of "safe search" setting through DNS alone.
From Guadalajara via Totalplay:
                   test1   test2   test3   test4   test5   test6   test7   test8   test9   test10  Average 24.20 38.20 39.30 39.90 41.10 42.80 52.70 59.50 76.70 85.40 279.50 391.50
Nice script, but 10 runs aren't enough to give reliable results. Not even close.
from Bhimavaram, India
  sh ./dnstest.sh |sort -k 22 -n test10  Average 46.60 51.00 56.30 56.30 56.40 56.40 57.10 57.10 57.40 59.20 59.80 141.90
Reply on news.ycombinator.com