check_http resolver (bug or me?)

[frank]

Try adding a trailing dot to the hostname you're resolving. That should 
prevent your resolver from trying to append your search domain(s) upon 
lookup. ie:

check_command     check_http_site!www.business-plan-maker.com.

-f

On Thu, 10 Mar 2005, Michael J. Pawlowsky wrote:

> Date: Thu, 10 Mar 2005 13:39:42 -0500
> From: Michael J. Pawlowsky <mikep at mi-consultants.com>
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] check_http resolver (bug or me?)
> 
> I just saw something interesting in my /var/log/messages regarding to named.
>
> Mar 10 12:57:19 www named[19993]: lame server resolving 
> 'www.business-plan-maker.com.mitimite.com' (
> in 'mitimite.com'?): 65.125.228.92#53
>
> mitimite.com is one of the completion domains that I have in resolv.conf.
> mitimite.com DNS is not on this server. Nor is it the same DNS server as 
> business-plan-maker.com.
>
> The only thing I can think of that is asking for the 
> www.business-plan-maker.com would be nagios.
>
> I have a chkcommand defined as:
>
> # 'check_http_site' command definition
> define command{
>       command_name    check_http_site
>       command_line    $USER1$/check_http -H $ARG1$
>       }
>
>
> And in services have:
>
> define service{
>       host_name               web1.chancetechnologies.com
>       service_description     check_http_site www.business-plan-maker.com
>       check_command           check_http_site!www.business-plan-maker.com
>       max_check_attempts      5
>       normal_check_interval   5
>       retry_check_interval    3
>       check_period            24x7
>       notification_interval   30
>       notification_period     24x7
>       notification_options    w,c,r
>       contact_groups          chancetech
> }
>
> For the fun of it I'm trying it in services as 
> check_http_site!www.business-plan-maker.com. (trailiing period).
> Would seem odd to nave to have a trailing period..   but worth a try.
> Anyone else notice perhaps some strange resolv behaviour from check_http?
>
> If I simply do a nslookup from the server were nagios is running all looks 
> well.
> ===============================================
> [root at www etc]# nslookup www.business-plan-maker.com
> Server:         192.168.5.50
> Address:        192.168.5.50#53
>
> Non-authoritative answer:
> Name:   www.business-plan-maker.com
> Address: 69.57.136.121
> ================================================
>
> Cheers,
> Mike
>
>
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at 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
>


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at 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