check_http adding domain name to fqdn ?

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
jlom
Posts: 17
Joined: Mon Dec 04, 2017 4:49 pm

check_http adding domain name to fqdn ?

Post by jlom »

Hi,

I have a weird problem I can't figure out why this would be happening.

I Have a site being checked with check_http every once in a while I am getting my domain added to the end of the FQDN.
[2018-05-21T08:17:10] SERVICE ALERT: name.domain.com;HTTP-Port80-slower-site;CRITICAL;SOFT;1;Temporary failure in name resolution

Here is the log from my DNS server which is how I know this is happening


2018-05-21T08:17:10-04:00 dns-1.net.domain.com named[15326]: client 123.123.123.1#56289 (commencement.domain.com.domain.com): query: commencement.domain.com.domain.com IN AAAA + (123.123.1.1)
User avatar
mcapra
Posts: 3739
Joined: Thu May 05, 2016 3:54 pm

Re: check_http adding domain name to fqdn ?

Post by mcapra »

Which version of check_http are you using? This should provide that information:

Code: Select all

/path/to/check_http --version
Which operating system and version of that operating system is doing the executing of check_http?

I'm pretty sure this is a general getaddrinfo failure that's happening here:
https://github.com/nagios-plugins/nagio ... ils.c#L207

Which would indicate this is a DNS related problem, possibly NXDOMAIN hijacking from some malicious actor (there's not much to gain, frankly), competing resolvers, or some other misconfigured aspect of name resolution on the machine itself.

I'm not totally convinced this is a check_http specific problem, but we'll do our due diligence.
Former Nagios employee
https://www.mcapra.com/
User avatar
cdienger
Support Tech
Posts: 5045
Joined: Tue Feb 07, 2017 11:26 am

Re: check_http adding domain name to fqdn ?

Post by cdienger »

+1 on a dns resolution issue. If a hostname cannot be resolved, it will try again but tack on the domain name found in /etc/resolv.conf.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Locked