Hi All,
I'm running Nagios v2.2 on a suse linux without Bind. When my first nameserver in resolv.conf fails, the Nagios checks start timing out. I get a mix of timeout errors and "no response" errors. This isn't really a big surprise since relying on resolv.conf is very slow when the DNS servers start dropping off. Of course, the name resolution works eventually but by then my 10-second timeout settings have given up. Has anyone using resolv.conf encountered and/or resolved this? Is Bind a requirement because of this? My decision to not go with Bind is because of the additional checking I get when Nagios does name resolution with each check. This approach has alerted us to numerous problems before getting that dreaded call from the customer. Any help or ideas would be greatly appreciated. - David Schlecht (dschl) ----------------------- The mailing list archive is found here: http://www.nagiosexchange.org/nagios-users.34.0.html ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Nagios-users mailing list [email protected] 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
