Health checks are not run if only one DNS server is benchmarked

codingsnippets / namebench

Automatically exported from code.google.com/p/namebench

Apache License 2.0

1 stars 0 forks source link

Health checks are not run if only one DNS server is benchmarked #132

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago

What steps will reproduce the problem?
1. Insert "62.101.93.101" in nameserver list, uncheck all the checkboxes, 
n.queries 10. 
2. Start benchmark

What is the expected output? 
- "The server tested is not healthy"

What do you see instead?
- XML indicating that it is the Fasted and with no problems.

What version of the product are you using? On what operating system?
1.3.1 RC4 - Windows 7 x32

Please provide any additional information below.

Using this input: "83.103.25.250, 62.101.93.101" I receive (correctly, I 
suppose): "None of the 2 nameserver are healthy".

Original issue reported on code.google.com by subvert...@gmail.com on 6 Jun 2010 at 9:40

GoogleCodeExporter commented 8 years ago

This is a surprising, but fully intended behavior. I added it so that I could 
quickly benchmark a single webserver, 
even if I wasn't on the internet. The correct approach would be to add a 
command-line option to skip all health 
tests. I will see about doing so for 1.4.

Original comment by helixblue on 6 Jun 2010 at 10:11

Changed title: Health checks are not run if only one DNS server is benchmarked
Changed state: Accepted

GoogleCodeExporter commented 8 years ago

Fixed in r1045 - will keep open until it hits a release.

Original comment by helixblue on 15 Jul 2010 at 1:16

Changed state: Started

GoogleCodeExporter commented 8 years ago

Hi. Please fix this! Our office only has one DNS server—others are 
blocked—and I want to benchmark it (I suspect it's acting weird).

Original comment by matt.hic...@gmail.com on 30 May 2013 at 3:24