Hmm, det här ser inte så bra ut.
Ibland säger verktyget att bara några DNSer är tillgängliga och ibland är nästan alla tillgängliga. Jag testade mot våra 2 interna DNSer som skickar förfrågan vidare till TDCs (Vår ISP) DNSer eller Googles 8.8.8.8
Testade samtidigt att köra mot TDCs och Googles DNSer direkt också. De var 100% tillförlitliga vilket inte de interna var under samma tillfälle.
Interna DNSerna snurrar på Win 2003 servrar
******************************************************************************************************************************
******************************************************************************************************************************
DNS Benchmark Conclusions & Recommendations
More than 20% of resolvers were unreliable?
Such a high percentage is suspicious: As you may have noticed, a relatively large number of the resolvers (2) benchmarked (more than one in every five) had apparent reliability problems. Since this is a suspiciously high number, it is more likely that the local network was busy and congested while the benchmark was running. Since this will produce unreliable timing results, you should probably attempt to re-run the benchmark at a time when the local network is quiet. Until then, you should consider these timing results to be invalid.
One or more system nameservers is NOT 100% reliable!
DNS reliability is extremely important, since lookup requests that are dropped and ignored by nameservers cause significant delays in Internet access while the querying system waits for a reply. The system is then finally forced to reissue the query to the same or to backup nameservers. While your system is patiently waiting for a reply, you are impatiently waiting to get on with your Internet access.
During this benchmark test, the nameservers being tested did not reply to some of the DNS queries they were sent.
So the question now is: Did the benchmark discover alternative nameservers having superior performance and reliability to which you could switch in order to obtain more performance and reliability?
Important Note:
Incorrect warnings of low reliability nameservers can arise if (1) DNS benchmarking is being performed while the local network is busy performing other work such as file downloading, or (2) the benchmark is running over a wireless (WiFi) link with low signal strength or high interference. Please try to minimize any other local network activity while the benchmark is running, and use a wired (not wireless) LAN connection if possible.
Recommended Actions:
Before you make any changes, you should probably run the benchmark a few more times at differing times of day to make sure that the troubling reliability is an ongoing problem and not just a brief occurrence.
You may also wish to consult the "Tabular Data" page which summarizes all benchmark results in numeric tables. The numbers make it easier to see exactly how unreliable your system's nameservers are compared with the available alternatives. (And also how the alternatives' performance compares.)
System nameserver is NOT replying to all queries!
One or more of this system's nameservers is not replying to all types of DNS Benchmark testing queries. You can determine what data are absent by noting which bars are missing from the bar chart, or looking for results missing from the "Tabular Data" page tables.
During the development of this DNS Benchmark we discovered that the routers used by some pre-release testers were not returning results for the benchmark's Uncached and/or Dotcom testing queries. Even though these queries are admittedly unusual, they are completely valid DNS queries. So the only conclusion was that those few routers were defective. Unfortunately, it appears that one or more of this system's current nameservers is similarly defective.
Recommended Actions:
During our testing, this trouble was only seen where consumer-grade routers were being used as DNS resolvers. Since most (though not all) small NAT routers make very poor DNS proxies, the best advice is usually to disable the router's own provisioning of DNS services and allow the ISP's DNS servers to be queried directly by the LAN's computers. This can generally be done through the router's configuration interface.
The firmware of consumer-grade NAT routers is often updated. So before making any changes, it is often worthwhile to verify that your router is using the latest release of its firmware and to update the router if it is currently using an older firmware release.
******************************************************************************************************************************
******************************************************************************************************************************