Red Hat Bugzilla – Bug 490691
nagios-plugins-dns doesn't check server specified with -s
Last modified: 2009-12-18 04:02:50 EST
Description of problem:
[root@vito ~]# /usr/lib/nagios/plugins/check_dns -s 184.108.40.206 -H www.kanarip.com
DNS OK: 1.013 second response time. www.kanarip.com returns 10.10.10.50|time=1.012664s;;;0.000000
[root@vito ~]# dig @220.127.116.11 www.kanarip.com
; <<>> DiG 9.5.1-P1-RedHat-9.5.1-1.P1.fc10 <<>> @18.104.22.168 www.kanarip.com
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39403
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.kanarip.com. IN A
;; ANSWER SECTION:
www.kanarip.com. 86342 IN CNAME pinky.kanarip.com.
pinky.kanarip.com. 86342 IN A 22.214.171.124
;; Query time: 1946 msec
;; SERVER: 126.96.36.199#53(188.8.131.52)
;; WHEN: Tue Mar 17 17:43:48 2009
;; MSG SIZE rcvd: 69
Version-Release number of selected component (if applicable):
[root@vito ~]# rpm -qv nagios nagios-plugins-dns
This is a Split DNS setup
This isn't rawhide... this is f10 ;-)
Come to think of it, I think it *does* check against the server specified, but since it's a CNAME, then tries to resolve locally while it should be using the same server.
[root@vito ~]# /usr/lib/nagios/plugins/check_dns -s 184.108.40.206 -H pinky.kanarip.com
DNS OK: 0.048 seconds response time. pinky.kanarip.com returns 220.127.116.11|time=0.048339s;;;0.000000
In nagios-plugins-dns-1.4.13-11.fc10.x86_64, looking at Wireshark it first queries the host specified with -s, then a second later queries the host listed in resolv.conf, thus always returning an OK even if the -s host is down/etc. (assuming the local resolver's working)
(In reply to comment #3)
> In nagios-plugins-dns-1.4.13-11.fc10.x86_64, looking at Wireshark it first
> queries the host specified with -s, then a second later queries the host listed
> in resolv.conf, thus always returning an OK even if the -s host is down/etc.
> (assuming the local resolver's working)
Actually, if check_dns is using /usr/bin/nslookup as strings suggests it is, nslookup behaves the same way if you pass a specific server to query on the command line - it falls back to the local resolver if the specified server fails.
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.