Nagios Support Forum

No DHCP, so I think we are golden!

Thanks!

I fixed the search domain in the resolv.conf file to reflect dhss.ak.local and it appears to have fixed it. Strange that the AD plugin, even when providing the FQDN of the DC, will strip that off and do a name lookup on just the server name.

Ok, to be a bit more specific... I am located in Anchorage, AK. We have domain controllers all over the state, due to the crappy connections that we have to deal with (some are on the back side of a saturated 56k connection to the WAN), we put a DC in that location so that those users aren't trying ...

See, I don't want this authenticating to a server that is over 400 miles away...i'm pretty serious that there are DCs all over the place because of the physical vastness of the WAN. I want to authenticate to hssancdc1 (which is in Anchorage, AK) and not hssfaidc1 (which is in Fairbanks, AK), on top ...

I think I know what's going on. The IP response from DNS for dhss.ak.local will cycle through 8 or 9 different addresses, as those are all the domain controllers on the network (which is spread over a large area). But I only want it to connect to the DC that is local, not any of the other DCs, as th...

[root@nagios-adc ~]# ping dhss.ak.local PING dhss.ak.local (146.63.206.85) 56(84) bytes of data. 64 bytes from hssfaidc1.dhss.ak.local (146.63.206.85): icmp_seq=1 ttl=121 time=35.6 ms 64 bytes from hssfaidc1.dhss.ak.local (146.63.206.85): icmp_seq=2 ttl=121 time=42.1 ms 64 bytes from hssfaidc1.dhss...

[root@nagios-adc ~]# ping hssancdc1.dhss.ak.local PING hssancdc1.dhss.ak.local (10.2.189.3) 56(84) bytes of data. 64 bytes from hssancdc1.dhss.ak.local (10.2.189.3): icmp_seq=1 ttl=127 time=0.973 ms 64 bytes from hssancdc1.dhss.ak.local (10.2.189.3): icmp_seq=2 ttl=127 time=0.461 ms 64 bytes from h...

Everything is setup correctly, but it only works when I put the IP address of the DC in the config. It won't work if I use the FQDN. When the FQDN is in the config, I try to log in and then run a netstat on the Nagios server, which lists the opendns.org connection on port 53.

Seeings as the defined primary and secondary DNS servers are the hosts of the dhss.ak.local namespace, of which they are also the domain controllers for the domain, I would HIGHLY doubt that it is a DNS problem. But, along those lines, here is the full response from nslookup on the nagios server: [r...