DNS IP failures after update to R12014

[tecnalb]

Hello,

I just updated to 2014R1.0

For the most part it seems like all is fine. But I have a couple of servers that are now indicating

DNS CRITICAL - expected 'host.domain.com.' but got ''

[sreinhardt]

Can you run "/usr/local/nagios/libexec/check_dns -h" and give me the version information please? I thought this was resolved after the beta testing, but would like to be sure.

[tecnalb]

[root@nagios mrtg]# /usr/local/nagios/libexec/check_dns -h
check_dns v2.0.1 (nagios-plugins 2.0.1)

[abrist]

Run the check from the cli, but give it a very verbose flag (-vvv). Post the output here.

[tecnalb]

This is the IP check.... so which way should this actually work? It was working until today's upgrade.

Should the check be checking the IP to the hostname or vice-verse?

IE

check_dns -H x.x.x.71 -a hostname

or

check_dns -H hostname -a x.x.x.71

This one always confuses me when I have an issue. Im thinking years ago I had a similar issue.

[root@nagios ~]# /usr/local/nagios/libexec/check_dns -vvv -H x.x.x.71
/usr/bin/nslookup -sil x.x.x.71
Server: x.x.x.3
Address: x.x.x.3#53

Non-authoritative answer:
71.x.x.x.in-addr.arpa name = host.domain.com.

Authoritative answers can be found from:
DNS OK: 0.007 seconds response time. x.x.x.71 returns |time=0.007072s;;;0.000000
[root@nagios ~]# /usr/local/nagios/libexec/check_dns -vvv -H x.x.x.71 -a host.domain.com
/usr/bin/nslookup -sil x.x.x.71
Server: x.x.x.3
Address: x.x.x.3#53

Non-authoritative answer:
71.x.x.x.in-addr.arpa name = host.domain.com.

Authoritative answers can be found from:
DNS CRITICAL - expected 'host.domain.com' but got ''
[root@nagios ~]#

[abrist]

Should the check be checking the IP to the hostname or vice-verse?

Run the cli check the same way the check is configured in XI.

Should the check be checking the IP to the hostname or vice-verse?

Depends. Are you trying to verify that a hostname resolves to a specific ip?

[tecnalb]

That doesn't help...sorry.

I didn't change anything. It has worked in all the 2012 versions. Now it doesn't in 2014.

[scottwilkerson]

@tecnalb - In order to determine where the problem is lying, we are going to need to see the command as it is in XI as well as the definition for the service.

Posting this on the forum is not ideal, so it would be best if you can send your profile from Admin -> System Profile to [email protected] along with the name of the host/service that is causing this, and we can have a tech take a look.

It is possible the your command is passing the -A flag, or their could be a bug in the plugin, but hard to know for sure without seeing the command.

Thanks.

[tecnalb]

Hello,

I've already opened a ticket to xisupport. So I'll leave these for you all to close at your discretion.


Thanks.

[scottwilkerson]

Thanks Jim. The team is going over your threads, and will be requesting some additional information..

Thanks for you patience as we help you get to the bottom if the issues you are having.

(Ticket#2014060310000108)