Dirk H. Schulz wrote:
Hi folks,
I have two servers running Nagios, one is 2.3.1 on Debian, the other 3.0.5
on CentOS. With both I have a peculiar problem:
Both of the servers have 3 different nameserves in /etc/resolv.conf, but
when the first nameserver fails, then more than half of the
Steve Burton wrote:
Dirk,
my solution was to run a slave name server on the Nagios server itself ,
restricted to only answer queries from localhost.
Steve.
Why not set something like options timeout:1 attempts:1 in
resolv.conf? From man resolv.conf:*
timeout:*/n/
sets the amount of time
Sean McAfee wrote:
Steve Burton wrote:
Dirk,
my solution was to run a slave name server on the Nagios server itself ,
restricted to only answer queries from localhost.
Steve.
Why not set something like options timeout:1 attempts:1 in
resolv.conf? From man resolv.conf:*
Steve Burton wrote:
Sean,
I reason I set up the slave server was so my nagios instance could
monitor the 'real' DNS servers by name and check the host and other
services on those hosts (they're Windows DCs) even if (or especially
if) the DNS service had failed.
That makes sense. We make
Hi folks,
I have two servers running Nagios, one is 2.3.1 on Debian, the other 3.0.5
on CentOS. With both I have a peculiar problem:
Both of the servers have 3 different nameserves in /etc/resolv.conf, but
when the first nameserver fails, then more than half of the service checks
fail (plugin
