Bug in check_dns

[Dale Clapperton (lists)]

Hi all

I believe I've found a bug in the check_dns tool, in that if you make a
query which is refused by the DNS server, check_dns returns OK.

Example dig, showing the query is refused:

su-2.05b$ dig www.intel.com @[server]

; <<>> DiG 8.3 <<>> www.intel.com @[server] 
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 4
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUERY SECTION:
;;      www.intel.com, type = A, class = IN

;; Total query time: 19 msec
;; FROM: [nagios host] to SERVER: [server]
;; WHEN: Fri Aug  1 13:00:22 2003
;; MSG SIZE  sent: 31  rcvd: 31

But when you run the same query on the same server with check_dns:

su-2.05b$ ./check_dns -H www.intel.com -s [server]
DNS ok - 0 seconds response time, Address(es) is/are (null)


Dale
-- 
Dale Clapperton (lists) <lists at blackbird.net.au>



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null