disabled fqdn not working
list Kris Springer
I just built a new xymon server that will only be used on an
internal network with 192 addresses. I have FQDN="FALSE" in the
xymonserver.cfg but the ping results shown on the xymon webpage show
that the tests are using names to test instead of IP's. Here's what
I've got in the hosts.cfg file.
192.168.1.1 Cisco-RV320-Router # !ssh https://192.168.1.1
The conn results aren't pinging 192.168.1.1, they're pinging the name 'Cisco-RV320-Router' which responds to some outside server I don't recognize. How do I force pinging to IP instead of name?
192.168.1.1 Cisco-RV320-Router # !ssh https://192.168.1.1
The conn results aren't pinging 192.168.1.1, they're pinging the name 'Cisco-RV320-Router' which responds to some outside server I don't recognize. How do I force pinging to IP instead of name?
Thank you.
------------------------------------------------
Kris Springer
list John Horne
▸
On Sat, 2018-09-01 at 08:07 -0600, Kris Springer wrote:
I just built a new xymon server that will only be used on an internal network with 192 addresses. I have FQDN="FALSE" in the xymonserver.cfg but the ping results shown on the xymon webpage show that the tests are using names to test instead of IP's. Here's what I've got in the hosts.cfg file. 192.168.1.1 Cisco-RV320-Router # !ssh https://192.168.1.1
The conn results aren't pinging 192.168.1.1, they're pinging the name 'Cisco-
RV320-Router' which responds to some outside server I don't recognize. How
do I force pinging to IP instead of name?
Use 'testip'. Example: ... # testip !ssh https://192.168.1.1 John. -- John Horne | Senior Operations Analyst | Technology and Information Services University of Plymouth | Drake Circus | Plymouth | Devon | PL4 8AA | UK [http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>; This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, University of Plymouth accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. University of Plymouth does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form.
![http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>](http://www.plymouth.ac.uk/images/email_footer.gif]<http://www.plymouth.ac.uk/worldclass>){kind=link}
list John Thurston
▸
On 9/1/2018 6:07 AM, Kris Springer wrote:
I just built a new xymon server that will only be used on an internal network with 192 addresses. I have FQDN="FALSE" in the xymonserver.cfg but the ping results shown on the xymon webpage show that the tests are using names to test instead of IP's.
The FQDN option doesn't affect how the xymonnet process performs its tests. It affects how client/host names are used by xymon. From the man:
FQDN : If set to TRUE, Xymon will use fully-qualified hostnames throughout. If set to FALSE, hostnames are stripped of their domain-part before being processed. It is highly recommended that you keep this set to TRUE. Default: TRUE
If what you are trying to do is make all the conn tests be performed by IP, you need to adjust the --dns option on xymonnet in your tasks.cfg
--dns=[ip|only|standard] With "--dns=ip" xymonnet will never do a DNS lookup; it will use the IP adresse specified in hosts.cfg for the tests.
--
Do things because you should, not just because you can.
John Thurston XXX-XXX-XXXX
user-ce4d79d99bab@xymon.invalid
Department of Administration
State of Alaska