DNS plugin problem

[Dan Hopkins]

> -----Original Message-----
> From: Skylar Thompson [mailto:skylar at cs.earlham.edu]
> Sent: 25 January 2005 01:22
> To: nagios-users at lists.sourceforge.net

> Subject: Re: [Nagios-users] DNS plugin problem
> On Mon, Jan 24, 2005 at 06:14:17PM +0000, Andy Smith wrote:
> > On Sun, Jan 23, 2005 at 03:14:02PM -0500, Skylar Thompson wrote:
> > > I'm using the check_dns plugin to monitor our BIND DNS 
> servers. Many times
> > > a day, the plugin marks one BIND server as down with this 
> error message:
> > > 
> > > SERVICE ALERT: hopper;DNS;CRITICAL;HARD;3;DNS CRITICAL - 
> '/usr/bin/nslookup
> > > -sil' output parsing exited with no address
> > > 
> > > It then comes back up about 10 minutes later:
> > > 
> > > SERVICE ALERT: hopper;DNS;OK;HARD;3;DNS ok - 1 seconds 
> response time,
> > > Address(es) is/are 216.109.118.74
> > 
> > Does the problem go away if you modify your check to use check_dig
> > instead?
> 
> Does check_dig use only the DNS servers listed on the Nagios 
> server? The
> DNS server in question is used by a separate subnet, but 
> we're responsible
> for monitoring their machines and services.

check_dig will use the server you identify with -H <hostname>

The default check_dns action uses the resolver(s) configured on the nagios
host, unless you override it with --server=<some dns server>

check_dns primary function is to verify a DNS entry, although it will verify
a specific server (poorly), hence the slightly confusing parameters

Dan


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
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