<div dir="ltr">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.<div><br></div><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><font face="courier new, monospace">search mydomain.suffix<br>nameserver 192.168.0.99<br>nameserver 192.168.0.98</font></blockquote></div><div><br></div></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr">- <a href="mailto:Tres.Finocchiaro@gmail.com" target="_blank">Tres.Finocchiaro@gmail.com</a></div></div>
<br><div class="gmail_quote">On Wed, Sep 17, 2014 at 10:38 AM, Kris Springer <span dir="ltr"><<a href="mailto:kspringer@innovateteam.com" target="_blank">kspringer@innovateteam.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>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.<span class=""><br>
<div>
<br>
<p><span>Thank you.</span></p>
<p><span>------------------------------------------------</span></p>
<p><span>Kris Springer<br>
</span></p>
<p><span><br>
</span></p>
<p><span><br>
<br>
</span>
</p>
</div></span><div><div class="h5">
On 9/16/2014 2:44 PM, Mark Felder wrote:<br>
</div></div></div><div><div class="h5">
<blockquote type="cite">
<pre>
On Tue, Sep 16, 2014, at 14:54, Kris Springer wrote:
</pre>
<blockquote type="cite">
<pre>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 <a href="http://myrouter.myddns.net" target="_blank">myrouter.myddns.net</a> # trace
0.0.0.0 NAS # noconn ssh "RCLIENT:cmd(ssh -T -i
/home/xymon/.ssh/xymon-rclient <a href="mailto:root@myrouter.myddns.net" target="_blank">root@myrouter.myddns.net</a>),ostype(linux)"
</pre>
</blockquote>
<pre>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 list
<a href="mailto:Xymon@xymon.com" target="_blank">Xymon@xymon.com</a>
<a href="http://lists.xymon.com/mailman/listinfo/xymon" target="_blank">http://lists.xymon.com/mailman/listinfo/xymon</a>
</pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
Xymon mailing list<br>
<a href="mailto:Xymon@xymon.com">Xymon@xymon.com</a><br>
<a href="http://lists.xymon.com/mailman/listinfo/xymon" target="_blank">http://lists.xymon.com/mailman/listinfo/xymon</a><br>
<br></blockquote></div><br></div>