DNS BenchmarkDNS Benchmark
Frequently Asked Questions & Answers
A page that hopes to eliminate any confusion that's been created.
divider
“You can't optimize it until you can measure it”
Please see the end of the page for DNS Benchmark version history.

Frequently Asked Questions

Q:Why does the DNS Benchmark contain many “red” (offline or actively rejecting) DNS resolvers?
A:Some fast (and useful) DNS resolvers are only accessible to some users on the Internet. An example might be those belonging to specific ISPs who have configured their resolvers for access only by their own customers. But during testing, we also discovered that some fast and useful resolvers were accessible to many users, but not others. Rather than exclude some potentially fast resolvers from the list, we decided to provide any that might be worthwhile, and allow the DNS Benchmark to determine whether they were accessible. Leaving the red marked resolvers in the Benchmark's list does not slow down the benchmarking, and they can be easily removed by right-clicking the mouse on the list and choosing "Remove dead nameservers."
Q:I'd like to use some fast DNS resolvers, but the Benchmark has colored them orange and their status is: “Bad domain names are intercepted by provider”. Does this mean I should not use them?
A:The DNS Benchmark colors working DNS resolvers orange when they do not return DNS errors in response to non-existent domain names. Instead, they return the IP address of a web “intercept page” that some ISPs and third-party DNS providers use to generate advertising and marketing revenue from their users' domain name “typos.” You can give the resolver a try by configuring your system to only use orange DNS resolvers, then deliberately mistype a domain name in your web browser and see how you feel about whatever it is that happens.

Note also that this behavior has raised enough stir among annoyed users that IPSs and third-party providers who are doing this often provide some means for turning off this behavior for individual customers. So if you would like to use “orange” resolvers, you might see whether there's a means for deactivating this behavior at the provider's end.
DNS Benchmark Version History

See the note below for information about the format of GRC's version numbering.
 
• [1.0.3824.0] – Initial version 1.0 release of the Benchmark.
Since the Benchmark's code was tested extensively in many environments by a large number of GRC's newsgroup participants prior to its release, we don't foresee many bug-fixing updates. But it might be that the Benchmark's users will have suggestions for modifications to the Benchmark's operation, or that the internal lists of resolvers and domain names will need updating.
 
• [1.1.3880.0] – Version 1.1 “Global Resolver List Scanner” release.
This release adds the major new capability of creating a custom “Top50” resolver list for the Benchmark to test. GRC is now maintaining a list of 4,845 DNS resolvers located around the world and the Benchmark's new “Resolver List Builder” system quickly scans evry one of these resolvers to find the potentially fastest 50. Anyone who is not already using a custom list will have this offered to them after a Benchmark is completed, and it is also possible to build or rebuild this list at any time from the Add/Remove nameservers dialog.

Additionally, this release updates and refines the Benchmark's built-in resolver list.


GRC's Version Numbering Format

GRC's newer software uses a version numbering system that is oriented toward automating the rapid distribution of incremental versions that are often rapidly produced during the program's development. Each of the four components has the following meaning:

[ MajorVersion . MinorVersion . DaysSince2000 . BuildOfDay ]
MajorVersionThis is the major version number of the program. It starts at 1 and is incremented by one whenever a significant enhancement in the operation of the program is released.
MinorVersionThis is the minor version number of the program. After each MajorVersion increment, the minor version is restarted at 0 and it is subsequently incremented by one whenever any smaller updates are made to the program. Since it is conceivable that the MinorVersion might not be changed if an insignificant change is made to the code, in such cases the third and fourth components (see next items) of the version number would still always differentiate the versions:
DaysSince2000This is the number of days since the start of year 2000 — with January 1st, 2000 UTC, being day zero — when the program was “built” (assembled, linked and published on the development computer). This numbering is independent of the settings for the MajorVersion and MinorVersion.
BuildOfDayThis is the 0-based “build number” for every publicly-released “build” occurring during the build day. The first time any new instance of the program is made public on a new UTC day, that instance will carry a BuildOfDay of zero (0). Subsequent publicly released builds will increment that number to differentiate them from each other.

GRC's DNS Benchmark Pages:

Jump to top of page
Gibson Research Corporation is owned and operated by Steve Gibson.  The contents
of this page are Copyright (c) 2010 Gibson Research Corporation. SpinRite, ShieldsUP,
NanoProbe, and any other indicated trademarks are registered trademarks of Gibson
Research Corporation, Laguna Hills, CA, USA. GRC's web and customer privacy policy.
Jump to top of page

Last Edit: Aug 16, 2010 at 14:32 (16.75 days ago)Viewed 17 times per day