An Icinga/Nagios plugin for #lotusknows what I mean

October 9th, 2009 | Categories: DNS, DomiNotes, Entertainement, Nagios | Tags: ,

I think I speak on behalf of Volker and Stefan, when I say that we have little hope that IBM/Lotus will ever fix what they buggered up. I for one, don't want to keep checking.

While waiting for a phone call, I whipped up a little Nagios / Icinga plugin to monitor the "progress" of the guys at the other end of the world.

Here you are:

#!/bin/sh
# check_borked_ibm_lotus_dns_developer_lotus_com.sh
# (C) 2009 Jan-Piet Mens
# Nagios Plugin to wait for ever.

WARNING=1
CRIT=2

NS="`dig +short lotus.com ns`"  # Find name servers
WHASSA=developer.lotus.com      # whattalookup?

for ns in ${NS}; do
   a=`dig +short @${ns} ${WHASSA}`  # Find A RR. Futile.

   # Next line can also be written as `[ true ]'
   [ "$a" != "192.147.107.27" ] && {
        echo -n "Holy cow, Joe! They fixed their friggin' DNS! Call Ed. "
        echo "Relax hon, they probably didn't fix, just changed sumpin'"
        exit ${WARNING};
        }
done
echo "Still borked. Waiting for SPR."
exit ${CRIT}

I do want to point out that above script contains loads of unnecessary ballast, and you can throw most of it out, leaving it like this:

#!/bin/sh

CRIT=2

echo "Still borked. Waiting for SPR."
exit ${CRIT}

Choose whichever version suits your environment best. ;-)

Astute readers will notice I didn't code an OK state; I don't think it'll be required any time soon…

  1. Chris Linfoot
    October 10th, 2009 at 11:57
    Reply | Quote | #1

    From here that CNAME appears now to have changed to an A RR pointing to 192.147.107.27. But now there's a new problem…

    GET / HTTP/1.1
    Host: developer.lotus.com

    HTTP/1.1 403 Forbidden by rule.
    Cache-Control: no-cache
    Pragma: no-cache
    Expires: Sat, 10 Oct 2009 09:50:32 GMT
    Last-Modified: Sat, 10 Oct 2009 09:50:32 GMT
    Content-Type: text/html
    Accept-Ranges: bytes
    Connection: close
    Date: Sat, 10 Oct 2009 09:50:32 GMT
    Server: IBM-PROXY-WTE/6.1
    Content-Length: 1391

    Looks like a reverse proxy at that IP doesn't want to play.

  2. October 10th, 2009 at 12:16
    Reply | Quote | #2

    Thanks for the wakeup call, Chris!