On 07/25/11 20:19, Yueh-Hung Liu wrote: > try this: > > check_dig -H "8.8.8.8" -l "-x 74.203.101.150" -T "PTR" -v > > you have to pass the "-x" option to the dig utility.
Interesting, I hadn't considered stringing together this, however check_dig returns a warning, which is because it's looking for: "-x 74.203.101.150" as the response. I guess if you tied it together with -a "somestring" you can make this setup work for you. For example: ./check_dig -H 8.8.8.8 -l "-x 74.203.101.150" -T PTR \ -a "akc.org" -v That returns OK, but without the -a, it returns a warning. -- Jonathan Angliss > > > > > > On Mon, Jul 25, 2011 at 9:37 PM, Chris C<mazzy...@gmail.com> wrote: >> Hi guys, >> I am having trouble getting a PTR record check working with check_dig >> >> check_dig fails.... >> check_dig -H "8.8.8.8" -l "74.203.101.150" -T "PTR" -v >> /usr/bin/dig @8.8.8.8 -p 53 74.203.101.150 -t PTR >> Looking for: '74.203.101.150' >> DNS CRITICAL - 0.169 seconds response time (No ANSWER SECTION >> found)|time=0.169224s;;;0.000000 >> >> >> dig works correctly.... >> dig @8.8.8.8 -x 74.203.101.150 >> >> ;<<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5<<>> @8.8.8.8 -x 74.203.101.150 >> ; (1 server found) >> ;; global options: printcmd >> ;; Got answer: >> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27441 >> ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0 >> >> ;; QUESTION SECTION: >> ;150.101.203.74.in-addr.arpa. IN PTR >> >> ;; ANSWER SECTION: >> 150.101.203.74.in-addr.arpa. 83707 IN CNAME >> 150.128-255.101.203.74.in-addr.arpa. >> 150.128-255.101.203.74.in-addr.arpa. 907 IN PTR akc.org. >> 150.128-255.101.203.74.in-addr.arpa. 907 IN PTR www.akc.org. >> >> ;; Query time: 15 msec >> ;; SERVER: 8.8.8.8#53(8.8.8.8) >> ;; WHEN: Mon Jul 25 09:07:21 2011 >> ;; MSG SIZE rcvd: 110 >> >> >> I can't get check_dig to work with any PTR record using any nameserver. >> >> Anyone have any idea what I'm doing wrong? >> >> Thanks, >> /Chris C >> >> ------------------------------------------------------------------------------ >> Storage Efficiency Calculator >> This modeling tool is based on patent-pending intellectual property that >> has been used successfully in hundreds of IBM storage optimization engage- >> ments, worldwide. Store less, Store more with what you own, Move data to >> the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/ >> _______________________________________________ >> Nagios-users mailing list >> Nagios-users@lists.sourceforge.net >> 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 >> > > ------------------------------------------------------------------------------ > Magic Quadrant for Content-Aware Data Loss Prevention > Research study explores the data loss prevention market. Includes in-depth > analysis on the changes within the DLP market, and the criteria used to > evaluate the strengths and weaknesses of these DLP solutions. > http://www.accelacomm.com/jaw/sfnl/114/51385063/ > _______________________________________________ > Nagios-users mailing list > Nagios-users@lists.sourceforge.net > 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 > ------------------------------------------------------------------------------ Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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