Académique Documents
Professionnel Documents
Culture Documents
Page 1 of 4
DNS Benchmark
DNS Benchmark
http://www.grc.com/dns/resources.htm
8/11/2012
Page 2 of 4
67.19.1.10 68.87.64.154 68.87.68.170 68.87.69.154 69.56.222.10 72.45.111.250 72.45.111.251 72.45.127.250 72.45.127.251 75.75.75.75 75.75.76.76 129.250.35.250 129.250.35.251 151.197.0.38 151.197.0.39 151.202.0.84 151.202.0.85 151.203.0.84 151.203.0.85 156.154.70.1 156.154.71.1 198.153.192.1 198.153.194.1 199.45.32.37 199.45.32.38 199.45.32.40 199.45.32.43 203.55.230.104 203.55.230.105 203.215.3.43 204.97.212.10 204.194.232.200 204.194.234.200 205.210.42.205 206.124.64.1 207.126.96.162 208.67.220.220 208.67.222.222 216.27.175.2 216.185.111.10 216.231.41.2 216.254.95.2
cache02.theplanet.com phil-dnssec-trial.inflow.pa.bo.comcast.net atlt-dnssec-trial.s3woodstock.ga.atlanta.comcast.net bvrt-dnssec-trial.beaverton.or.bverton.comcast.net cache02.theplanet.com xplr-72-45-111-250.xplornet.com xplr-72-45-111-251.xplornet.com xplr-72-45-127-250.xplornet.com xplr-72-45-127-251.xplornet.com cdns01.comcast.net cdns02.comcast.net x.ns.gin.ntt.net y.ns.gin.ntt.net nsphil.bellatlantic.net home4.bellatlantic.net nyc1-qwest.bellatlantic.net nyc2-qwest.bellatlantic.net boston1-qwest.bellatlantic.net boston2-qwest.bellatlantic.net rdns1.ultradns.net rdns2.ultradns.net --- no official Internet DNS name ----- no official Internet DNS name --world1.bellatlantic.net nsdc.bellatlantic.net legacy-ns1.bellatlantic.net home1.bellatlantic.net per-qv1-dnsradius5.iinet.net.au per-qv1-dnsradius6.iinet.net.au syd-stl-cns1.iinet.net.au ns3.sprintlink.net --- no official Internet DNS name ----- no official Internet DNS name --cache1.dnsresolvers.com bigguy.gte.net ns.above.net resolver2.opendns.com resolver1.opendns.com dns.atl1.speakeasy.net cache01.theplanet.com ns-legacy.speakeasy.net dns.nyc1.speakeasy.net
Note that a current list used by any future version of this benchmark can easily be obtained by running the benchmark, deleting all current system and public resolvers, adding back only the public resolvers (this must be done in this sequence because there could be an overlap between the system and public resolver lists), then using the System Menu to Save Nameserver to .INI file, thus saving the Benchmark's current public resolver list as an .INI file . . . which will be a text file formatted as shown above. You can then edit the file to add or remove any resolvers. Once you have an updated list, you may:
Give the file the same name as the executable file, but with the file extension .ini, and place it into the executable file's directory to cause the Benchmark to load that file automatically upon start-up. Use the command-line options to automatically load this file whenever the Benchmark
http://www.grc.com/dns/resources.htm
8/11/2012
Page 3 of 4
is started.
We expect this built-in list to evolve over time as we receive feedback from DNS Benchmark users. If our Benchmark's users provide any locale-specific publicly accessible resolver lists, such as for specific geographic regions of the Internet, we will use this page to share them with all other Benchmark users.
That default domain name list is contained in this simple text file: domains.txt. Since the need to alter this default domains list should be much more rare than altering the system's default resolver list, no provision for replacing the list was built into the Benchmark's user-interface. However, as was detailed on the command-line options page, the /domains command-line option can be used to replace the Benchmark's builtin list with any alternative user-provided list. IMPORTANT NOTE: The Benchmark computes and achieves important statistical significance from its benchmark analysis only by acquiring a sufficient number of timing samples from each tested resolver. During the Benchmark's extensive developmental testing, fifty (50) domain lookups per resolver was found to provide the optimal mixture of statistical significance, results repeatability, and total benchmark running time. Consequently, if the Benchmark's built-in domains list is replaced with one having many fewer than fifty (50) domains, the benchmark will run faster overall, but it will also produce lower reliability results. And, conversely, if a domain list consisting of more domains were used instead of the Benchmark's current fifty (50) domains default list, the Benchmark's total running time would be increased, but the statistical significance of its results will be improved for increased accuracy.
http://www.grc.com/dns/resources.htm
8/11/2012
Page 4 of 4
Here is a list of the top 100 domains (100domains.txt) which could be used to obtain a higher level of statistical significance. Warning! This list has NOT been pruned for possibly-objectionable domain names, so any computer running the Benchmark with this list will apparently be looking up the IPs of all of these domains! This might not be appropriate for use in a corporate setting.
As with the resolver list above, if our Benchmark's users provide any interesting specialpurpose lists of domain names, such as locale-specific domains for specific geographic regions, we will use this page to share them with all other Benchmark users.
1 DNS Benchmark Introduction 2 Features & Operation Walkthrough 3 System Menu Options & Commands 4 Command-Line Operation Reference 5 Building a Custom Nameserver List 6 DNS Benchmark Resource Files
7 Configuring your DNS Nameservers 8 Benchmark Questions & Answers 9 DNS Benchmark Version History 10 Running GRC Apps under WINE 11 DNS Spoofability Test Introduction 12 Please Send Us Your Feedback
Gibson Research Corporation is owned and operated by Steve Gibson. The contents of this page are Copyright (c) 2012 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. Last Edit: Jun 18, 2010 at 08:47 (785.03 days ago) Viewed 9 times per day
http://www.grc.com/dns/resources.htm
8/11/2012