Downloads of v 1.3.6668.20190425:


Last Update:

29 Apr 2019

Package Maintainer(s):

Software Author(s):

  • Steve Gibson


domain name server dns speed benchmark steve gibson portable

DNS Benchmark

  • 1
  • 2
  • 3

1.3.6668.20190425 | Updated: 29 Apr 2019



Downloads of v 1.3.6668.20190425:



Software Author(s):

  • Steve Gibson

  • 1
  • 2
  • 3
DNS Benchmark 1.3.6668.20190425

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Passed


Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.


To install DNS Benchmark, run the following command from the command line or from PowerShell:


To upgrade DNS Benchmark, run the following command from the command line or from PowerShell:


To uninstall DNS Benchmark, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade dns-benchmark -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade dns-benchmark -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure dns-benchmark installed
    name: dns-benchmark
    state: present
    version: 1.3.6668.20190425
    source: STEP 3 URL

See docs at

chocolatey_package 'dns-benchmark' do
  action    :install
  version  '1.3.6668.20190425'
  source   'STEP 3 URL'

See docs at

    Name: dns-benchmark,
    Version: 1.3.6668.20190425,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller dns-benchmark
   Name     = 'dns-benchmark'
   Ensure   = 'Present'
   Version  = '1.3.6668.20190425'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'dns-benchmark':
  provider => 'chocolatey',
  ensure   => '1.3.6668.20190425',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install dns-benchmark version="1.3.6668.20190425" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator gep13 on 09 May 2019.



To use choco:// protocol URLs, install (unofficial) choco:// Protocol support

Screenshot of DNS Benchmark

What is GRC's DNS Benchmark?
GRC's DNS Benchmark performs a detailed analysis and comparison of the operational performance and reliability of any set of up to 200 DNS nameservers (sometimes also called resolvers) at once. When the Benchmark is started in its default configuration, it identifies all DNS nameservers the user's system is currently configured to use and adds them to its built-in list of publicly available “alternative” nameservers. Each DNS nameserver in the benchmark list is carefully “characterized” to determine its suitability — to you — for your use as a DNS resolver. This characterization includes testing each nameserver for its “redirection” behavior: whether it returns an error for a bad domain request, or redirects a user's web browser to a commercial marketing-oriented page. While such behavior may be acceptable to some users, others may find this objectionable.

The point made above about the suitability — to you — of candidate nameservers is a crucial one, since everything is about where you are located relative to the nameservers being tested. You might see someone talking about how fast some specific DNS nameservers are for them, but unless you share their location there's absolutely no guarantee that the same nameservers would perform as well for you. ONLY by benchmarking DNS resolvers from your own location, as this DNS Benchmark does, can you compare nameserver performance where it matters . . . right where you're computer is.
When the benchmark is run, the performance and apparent reliability of the DNS nameservers the system is currently using, plus all of the working nameservers on the Benchmark's built-in list of alternative nameservers are compared with each other.

Results are continuously displayed and updated while the benchmark is underway, with a dynamically sorted and scaled bar chart, and a tabular chart display showing the cached, uncached and “dotcom” DNS lookup performance of each nameserver. These values are determined by carefully querying each nameserver for the IP addresses of the top 50 most popular domain names on the Internet and also by querying for nonexistent domains.

Once the benchmark finishes, the results are heuristically and statistically analyzed to present a comprehensive yet simplified and understandable English-language summary of all important findings and conclusions. Based upon these results, users may choose to change the usage order of their system's own resolvers, or, if alternative public nameservers offer superior performance or features compared with the nameservers currently being used, to switch to one or more alternative nameservers.


Click here to Patreon-ize the package maintainer.

$ErrorActionPreference = 'Stop'
$packageName = 'dns-benchmark' 
$toolsDir    = $(Split-Path -parent $MyInvocation.MyCommand.Definition)

Install-ChocolateyShortcut -shortcutFilePath "$ENV:Public\Desktop\DNS Benchmark.lnk" -targetPath "$toolsDir\DNSBench.exe"
Install-ChocolateyShortcut -shortcutFilePath "$ENV:ProgramData\Microsoft\Windows\Start Menu\Programs\DNS Benchmark.lnk" -targetPath "$toolsDir\DNSBench.exe"
$ErrorActionPreference = 'Stop'
$packageName= 'dns-benchmark' 

Remove-Item "$ENV:Public\Desktop\DNS Benchmark.lnk" -Force -ErrorAction SilentlyContinue
Remove-Item "$ENV:ProgramData\Microsoft\Windows\Start Menu\Programs\DNS Benchmark" -Force -ErrorAction SilentlyContinue
md5: AF51A7986FB95093BB1D65A3B7ECB98A | sha1: 8A19710E3DE2894E394484C08F777D997D02A5E5 | sha256: A9BC505F668A6AF598681A0EB1BE64B484D869A48B5991107827A9F0052CFF45 | sha512: 07895BE0E31D6F91AD05A41FE8AE122BA5D7CD648A9714A5096D41501C85532E8C7B238AF177EFB79E2E35B5AE3507A7BAD5DA8B563F416429B0307A1508B0FF
============================== DNS Benchmark ==============================

From inside the DNS Benchmark program under the Introduction tab:

Please Note: This program is Copyright (c) 2010 by Gibson Research Corporation -- ALL RIGHTS RESERVED. This program is FREEWARE. Although it may not be altered in any way, it MAY BE FREELY COPIED AND DISTRIBUTED onto and through any and all computer media in ANY form or fashion. You are hereby granted the right to do so.

============================== DNS Benchmark ==============================
============================== DNS Benchmark ==============================

bcurran3 downloads and packages the executable for Domain Name Speed Benchmark from:

============================== DNS Benchmark ==============================

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
DNS Benchmark 1.3.6668.0 653 Sunday, April 22, 2018 Approved
DNS Benchmark 1.2.3925.20161106 610 Sunday, November 6, 2016 Approved
DNS Benchmark 1.2.3925.20160918 348 Monday, September 19, 2016 Approved
DNS Benchmark 1.2.3925.0 408 Saturday, April 16, 2016 Approved

This package has no dependencies.

Discussion for the DNS Benchmark Package

Ground Rules:

  • This discussion is only about DNS Benchmark and the DNS Benchmark package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or DNS Benchmark, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus