Hey... I'm the OP. We're using a mix of client tools. For Windows
systems (which aren't affected by this) we use nsclient++. For our Linux
servers, NRPE... for UNIX (Solaris) and OS X we're using check_by_ssh.
Both the NRPE and check_by_ssh clients are affected by this.
I'm willing to give the
I don't know if I'm misreading the OP, but if the plugins start timing out
on only the boxes whose primary DNS is being rebooted, would adding a
caching DNS server to the Nagios box really make a difference?
I think the root cause to these timeouts is that the Nagios plugin timeout
is happening be
On Jun 9, 2009, at 10:42 AM, Randal, Phil wrote:
> Option 5: Install a local caching DNS server on your nagios box,
> and put 127.0.0.1 at the top of resolv.conf.
My reading of the issue, and I believe that I've seen it in the past
as well, is that the problem isn't with DNS resolution on t
Really the best choice is to using caching DNS on the Nagios
server. I'd recommend dnsmasq, it just does caching locally without
needing to do big zone transfers. It has low overhead and simple
configuration as a result.
Enjoy.
On Tue, Jun 09, 2009 at 11:19:20AM -0400, Andrew Davis wrote:
> I've
this e-mail in error please
contact the sender immediately and destroy all copies of it.
From: Andrew Davis [mailto:ncc...@gmail.com]
Sent: 09 June 2009 16:19
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] DNS down and false alerts...
I'v
I've observed an interesting issue with Nagios. Our environment is a mix
of UNIX, Linux, Apple, and Windows. The core of the network is Active
Directory including two AD servers that are both our primary, internal
DNS servers. All non-Windows systems have a resolv.conf that looks like:
*nam
