[ nagiosplug-Feature Requests-3569503 ] check_dig: option to require flag is set
SourceForge.net <[email protected]>
| Newsgroups | gmane.network.nagios.plugins.devel |
|---|---|
| Message-ID | <[email protected]> |
Feature Requests item #3569503, was opened at 2012-09-19 06:45 Message generated for change (Tracker Item Submitted) made by ulrik_haugen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397600&aid=3569503&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Priority: 5 Private: No Submitted By: Ulrik Haugen (ulrik_haugen) Assigned to: Nobody/Anonymous (nobody) Summary: check_dig: option to require flag is set Initial Comment: I'd like an option to check_dig to require that a flag is set in the reply. This would be of use when checking signed records to insist that the ad flag is set in the reply. While you can just use a validating resolver and expect check_dig to complain about answer missing this gives no warning if the resolver should stop validating for any reason. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397600&aid=3569503&group_id=29880 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________________ Nagios Plugin Development Mailing List Nagiosplug-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Unsubscribe at https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel ::: Please include plugins version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null