Re: [Bigsister-general] dns test bug

[Kai S. <mai...@co...>]

Thomas Aeby wrote on Wed, 2 Dec 2015 17:10:10 +0100:

> That's because it's one of the "old style" tests. And there is no
> manpage either :-(

Yeah, I couldn't find any documentation on syntax. Only the one I used in my 
config file and a few mentions on the mailing list, but no example. So I dug for 
the code.

> Indeed, that's very limitted and does result in a problem if you are
> monitoring a DNS server which does not resolve uxmon's host.

Ah, well, thinking about this a second time I now understand how the config was 
supposed to be done. I was using it the wrong way! I used the IP number for the 
nameserver. This way it did a reverse dns lookup against itself, which didn't 
work all the time, anyway. But the remote dns gave a NOERROR back, so it 
succeeded for bs. Now the ns vendor made a new release and changed this to error 
code REFUSED - which made bs go red and me have a look.

So, using something like

ns1.example.org(DNS) host=ns1.example.org dns

should have worked. But I used the IP number. I know this or a similar config 
line used to work years ago, but then I had a problem, asked on the list and came 
up with the query= syntax which worked (but not in the intended way, which I 
didn't notice).

Here's what you should use for syntax with the corrected code you checked in:

hostname or IP number(bs hostname)  query="host or zone to be checked" 
host="nameserver hostname or IP number" item="column in monitoring display" dns

> Other nice things to do in a DNS check: check zone consistency via SOA queries.

You mean, check master and slave zones for same version? Yeah, if you check a lot 
of domains, this might be helpful. I just want to check if the nameserver is up 
and responds.

Cheers to you both!


Kai

-- 
Get your web at Conactive Internet Services: http://www.conactive.com