writing your own plugin here is the way to go if you can't find anything on nagiosexchange.org, and I think the dig suggestion is a good start.
Why would you need to check this though? Shouldn't it be set once and then stay ok after your deploy + test? My records are tested at deploy time and then I just have to check that the dns servers are up which is a more common task. -h Hari Sekhon August Simonelli wrote: > i think check_dig might start things off ... you can ask a name server > for an MX record and specify what you expect in the answer section > with the -a flag: > > check_dig -H SERVER -l cnn.com <http://cnn.com> -T mx -a > nycmail1.turner.com <http://nycmail1.turner.com> > > so this would expect the string "nycmail1.turner.com > <http://nycmail1.turner.com>" to be in the answer section ... > > but i can only see how to get the lowest MX record with check_dig so > seeing higher MX may require a little extra work ... > > > > On 7/27/07, *Rogelio Bastardo * <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > On various DNS servers, I'd like to make sure that a certain A > records > remains the 10 record (or, at least, the first deliverable mail > server), > and then alert me when that changes. > > Any idea how to do this with Nagios? From what I can tell, the > check_dns plugin does not have this functionality. > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ 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
