We use the term “Public” to refer to all other nameservers that are not currently configured for use by the local system. Throughout these pages, and throughout the DNS Benchmark, we use the term “System” nameserver to mean any DNS server that is currently configured for use by the local system upon which the Benchmark is being run. ![]() So, when we refer to a DNS server, a nameserver, or a resolver, we always mean the same thing: an Internet DNS resolving nameserver that responds to and answers DNS queries at a given IP address. These pages will continue this flexible practice, choosing whichever name seems to flow best in the context. Two Notes About Terminology:DNS resolving nameservers (the things this utility tests, characterizes, and benchmarks) are commonly referred to as “DNS servers”, “DNS nameservers”, or “DNS resolvers”, sometimes without the “DNS” prefix. if you have some time to invest, and your goal is to seriously adopt this powerful tool as a component of your permanent bag of tricks, there are sufficient subtleties and “extras” hidden inside this quite comprehensive application that taking some time to make sure you haven't missed anything important might be time well spent. So if you are willing to just read the text presented on the benchmark's various tabbed pages - for example, please be sure to read the “Introduction” tab's text just once and be sure to read the “Conclusions” tab after the Benchmark is finished - you can probably safely ignore the rest of these web pages. That is, after all, the whole point and wonderful benefit of a graphical user interface (GUI). Our DNS Benchmark utility has been designed, as we design everything, so that the average user can just jump in without “reading the manual” and pretty much figure it all out for themselves. ![]() “You can't optimize it until you can measure it”
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |