[Nagiosplug-devel] check_dns

[Awais Ahmad]

Sure, I'll do this, this weekend. BTW, are the resolver libs not 
available via libc on FreeBSD?


Cheers

Awais


On Tue, 2004-03-02 at 08:26, Voon, Ton wrote:
> Awais,
> 
> I had a go at this yesterday, but have to admit abject failure. I couldn't
> get your patch to r1.3.1 to compile correctly on my MacOSX system, but I
> think it is running bind 9 and there are some compatibility #defines I think
> I need to set. 
> 
> Got further on SF's FreeBSD system with these changes:
> 
> - compile with -lresolv
> - put an if (target) around the _res.nscount to only set the nameserver if
> specified with -s
> 
> But I am absolutely baffled how to expand out the DNS reply - too
> complicated for me! I specifically want to catch multiple IP addresses
> (ibm.com is a good example) which is in the current functionality.
> 
> Could you provide a patch to HEAD? 
> 
> Ton
> 
> -----Original Message-----
> From: Awais Ahmad [mailto:awais at eurobell.net] 
> Sent: Monday, February 23, 2004 12:37 PM
> To: Karl DeBisschop
> Cc: NagiosPlug Devel
> Subject: Re: [Nagiosplug-devel] check_dns
> 
> 
> I have done this with the stable version of check_dns.c but never had
> the time to carry the changes across to HEAD. The patch is attached.
> 
> Although the main resolver lib functions are available, via
> GLIBC/LIBC,the response parsing routines (ns_parserr and friends) are
> only visible to the resolver lib functions themselves. 
> I've had to roll my own. 
> 
> I've tested on Debian GNU/Linux, Redhat GNU/Linux, FreeBSD current/4.X
> and Solaris 7.
> 
> 
> Awais Ahmad
> 
> 
> 
> 
> 
> 
> On Fri, 2004-02-20 at 03:52, Karl DeBisschop wrote:
> > On Thu, 2004-02-19 at 22:34, Ton Voon wrote:
> > 
> > > I'll have a go at this change, but only after I can get check_dns to 
> > > use the resolver routines instead of nslookup first. Most of 
> > > check_dns.c looks like it is parsing for error messages in nslookup!
> > 
> > Makes sense to me. That was the direction we wanted to go anyway, to use
> > the resolver instead of parsing scripts.
> > 
> > IIRC, the resolver is covered by POSIX, so we should have much less
> > platform-specific cruft once we do that.
> > 
> > --
> > Karl
> > 
> > 
> > 
> > -------------------------------------------------------
> > SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> > Build and deploy apps & Web services for Linux with
> > a free DVD software kit from IBM. Click Now!
> > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> > _______________________________________________
> > Nagiosplug-devel mailing list
> > Nagiosplug-devel at lists.sourceforge.net
> > 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
> > 
> 
> 
> This private and confidential e-mail has been sent to you by Egg.
> The Egg group of companies includes Egg Banking plc
> (registered no. 2999842), Egg Financial Products Ltd (registered
> no. 3319027) and Egg Investments Ltd (registered no. 3403963) which
> is authorised and regulated by the Financial Services Authority. Egg
> Investments Ltd. is entered in the FSA register under number 190518. 
> 
> Registered in England and Wales. Registered offices: 1 Waterhouse
> Square, 138-142 Holborn, London EC1N 2NA.
> 
> If you are not the intended recipient of this e-mail and have received
> it in error, please notify the sender by replying with 'received in
> error' as the subject and then delete it from your mailbox.
> 
> 
> 
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Nagiosplug-devel mailing list
> Nagiosplug-devel at lists.sourceforge.net
> 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
>