![]() If a user objects to this information being returned to GRC, they may start the Benchmark with the '/nosend' option to suppress this transmission. Over time this will allow GRC to eliminate those resolvers that have never made it into anyone's top 50 list from its master list so that the custom list building will be faster for everyone. In order to assemble a database of the world's most useful DNS resolvers, at the same time as the “top 50 fastest resolvers” are determined and built into a final list, by default the Benchmark also sends a list of the top 200 fastest resolvers found by the scanning process back to GRC. The /nosend command instructs the Benchmark not to send the list of the 200 fastest resolvers, resulting from the user's building or re-building of a custom nameserver list, back to GRC. At some point in the future, when DNSSEC is more widely supported, this feature will likely be enabled by default, with an option to disable when needed. You should, therefore, test the use of this option carefully and perhaps use it only with resolvers that are capable of resolving DNSSEC-enabled queries. Note: At the time of this benchmark's initial release (June, 2010) DNSSEC support is so poor that enabling this option will cause many of the resolvers on the Benchmark's default list to fail catastrophically. Furthermore, if you wished to always have DNSSEC enabled, you could create a Windows shortcut that specifies this option in the shortcut so that it would always be enabled by default whenever the Benchmark was started by using the shortcut. Including this command on the command-line is equivalent to enabling the DNSSEC option through the Benchmark's user-interface, so this command allows DNSSEC to be used during automated testing (where no user-interface is present). The /dnssec command instructs the Benchmark to employ the DNSSEC security extensions in the queries it generates. After extensive testing and statistical analysis, a list of fifty (50) domains was chosen as the best compromise between speed and reliable results. Conversely, increasing the length of the list would increase the total running time while producing somewhat more consistent results. Note: Although using fewer than fifty (50) domain names will shorten the Benchmark's total running time, fewer test samples will reduce the accuracy and reproducibility of the benchmark's results. The domain names used by the Benchmark were chosen for their worldwide popularity with any potentially offensive or controversial domains removed. You may freely edit the file, adding or subtracting domains as you choose, or completely replacing it with a list of your own. The default domain name list is contained in this simple text file: domains.txt. If you wished to test various specific lists of nameservers automatically, you might use a command of this form: The /add command adds the indicated IP, or list of IPs, to the benchmark's list of nameservers to test. This is identical to the default start-up action, which loads both the system's locally configured nameservers and the Benchmark's built-in list of nameservers. The token “all” to specify both “system” and “public” at once.The token “public” to specify the Benchmark's built-in list of nameserver IPs.The token “system” to specify all of the system's currently configured nameservers.An explicit IP address in dotted IP format (1.2.3.4).(You can create a valid sample IP list by using the Benchmark's “Save Nameservers to INI file” command.) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |