On Feb 15, 2022, at 11:28, John Thurston <user-ce4d79d99bab@xymon.invalid> wrote:
'tis in the man page for hosts.cfg, but I'll paste it here for ready reference:
*dns*
Simple DNS test. It will attempt to lookup the A record for the hostname of the DNS server.
Which means the test performed by xymonnet is attempting to look up an A-record for the name "walkie" and failing. It is doing something like:
dig +short +notcp A walkie @10.24.38.132
Either change your hostname to a fully-qualified domain name (FQDN) (e.g. walkie.foo.bar.com), or change your DNS test to use the long-form:
*dns=TYPE:lookup[,TYPE:lookup...]*
The default DNS tests will attempt a DNS lookup of the DNS' servers own hostname. You can specify the hostname to lookup on a DNS server by listing it on each test.
That would make the right side of your line look like:
dns=A:walkie.foo.bar.com
--
Do things because you should, not just because you can.
John Thurston XXX-XXX-XXXX
user-ce4d79d99bab@xymon.invalid
Department of Administration
State of Alaska
On 2/14/2022 11:38 PM, Ian Diddams via Xymon wrote:
if we set a hosts.cfg line
10.24.38.132 walkie # ssh dns
we can expect xymon to check that ssh connections exist for thats erver, and also does some sort of dns check.
what exactly IS this check?
becasue the dns on that server is runjning fine - but the xymon alert shopws red.