We successfully use resolv.conf. It works well for resolving some
important virtual machines that are registered with DNS but IPs may change.
Xymon works well with this. Too well in some cases as Xymon seems to
resolve hostname first. We quickly found incorrect DNS records when they
showed as red but were in fact green.
search mydomain.suffix
nameserver 192.168.0.99
nameserver 192.168.0.98
- user-88678e65ced1@xymon.invalid
On Wed, Sep 17, 2014 at 10:38 AM, Kris Springer <user-c2caa0a7a8d5@xymon.invalid>
wrote:
That's a great idea but I run into the same issue. The /etc/hosts file
wants an IP too. It doesn't seem to want to just link a short name to a
fqdn. I've looked into possibly using the resolv.conf to do what I want
but haven't seen any examples of it actually working. Oh well. It's not
that important.
Thank you.
Kris Springer
On 9/16/2014 2:44 PM, Mark Felder wrote:
On Tue, Sep 16, 2014, at 14:54, Kris Springer wrote:
Anyone know how to test ssh using a domain name instead of an IP? I'm
using the rclient and monitoring NAS devices that are remote and behind
port forwarded DHCP home routers that have DDNS names so I have 0.0.0.0
for the host IP's in the hosts.cfg file. I just want to test ssh to the
DDNS name, not the IP. The NAS host line in my hosts.cfg is not using a
FQDN as the hostname because that gets checked as a separate host.
Here's a sample of what I have in my hosts.cfg file.
0.0.0.0 myrouter.myddns.net # trace
0.0.0.0 NAS # noconn ssh "RCLIENT:cmd(ssh -T -i
/home/xymon/.ssh/xymon-rclient user-7bd5c34c7476@xymon.invalid),ostype(linux)"
If the server can resolve the hostname it will use that for the tests.
If you put NAS in your /etc/hosts file I believe it should work.
Xymon mailing user-d459c9d661b6@xymon.invalid