bbtest-net man page says

   --dns=[ip|only|standard]
          Determines how bbtest-net finds the IP adresses of the

hosts to test. By default (the "standard"), bbtest-net does a DNS lookup of the hostname to determine the IP address, unless the host has the "testip" tag, or the DNS lookup fails. With "--dns=only" bbtest-net will ONLY do the DNS lookup; it it fails, then all services on that host will be reported as being down. With "--dns=ip" bbtest-net will never do a DNS lookup; it will use the IP adresse specified in bb-hosts for the tests. Thus, this setting is equivalent to having the "testip" tag on all hosts. Note that http tests will ignore this setting and still perform a DNS lookup for the hostname given in the URL; see the "bbtest-net tags for HTTP tests" section in bb-hosts(5)

I think this should be updated like below. added a "Note:.."

   --dns=[ip|only|standard]
          Determines how bbtest-net finds the IP adresses of the

hosts to test. By default (the "standard"), bbtest-net does a DNS lookup of the hostname to determine the IP address, unless the host has the "testip" tag, or the DNS lookup fails. With "--dns=only" bbtest-net will ONLY do the DNS lookup; it it fails, then all services on that host will be reported as being down. With "--dns=ip" bbtest-net will never do a DNS lookup; it will use the IP adresse specified in bb-hosts for the tests. Thus, this setting is equivalent to having the "testip" tag on all hosts. Note that http tests will ignore this setting and still perform a DNS lookup for the hostname given in the URL; see the "bbtest-net tags for HTTP tests" section in bb-hosts(5) Note: for dns standard, If DNS lookup fails, hobbit picks the IP from the bb-hosts file for all network tests like ping and etc.

In hobbit server even though dig @192.168.1.1 host.example.net gives no answer where 192.168.1.1 is the resolver. But ping test still shows success. There is no entry for host.example.net in hobbit server's /etc/hosts either.

-- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?