NetXMS Support Forum

Hi,

I have 2 test servers running netxms to monitor windows pc's.
The windowd pc's are configured to get an IP from a Dhcp server.

When the host (with netxms client installed) is discovered the primary hostname is always set to the IP address and not the DNS name.

my netxms server connects to a client over wan. The client is configured as proxy server for the other clients in te network.

Is there someone using the option? UseDNSNameForDiscoveredNodes = 1 and did that work?

Regards

Denis

Hi!

UseDNSNameForDiscoveredNodes set to 1 should help. However, you must ensure that reverse DNS is working correctly. When network discovery is working, NetXMS server got an IP address. If UseDNSNameForDiscoveredNodes set to 1, server tries to resolve IP address to DNS name. If succeeds, it tries to resolve this DNS name back into IP address. If resolved IP matched with originally discovered IP, DNS name accepted as node's primary host name. If any of these steps fails, IP address will be sued as primary host name.

Best regards,
Victor

Hi,

I still have problems with hostnames/ DNS resolving.

for me the reverse DNS is ok in the network

Ping Myhost1 i get reply from the host.
when in do
ping -a x.x.x.x I get the hostname back in the ping.

Now on a site we have changed the iprange.
we connect to the hosts in the network with a netxms proxy.

When we do a ping to a client by name on the proyx we will get the new ip of the host.
But it isn't possible to connect to the other hosts.
If I have a look in the object properties of a client:
Primary host name : MyHost1
Primary IP Address: 192.168.0.54 (the old range)

The only way to reconnect with the host is to change the Primary Host Name with the new IP then I see direct that the primary IP address als change to 192.168.6.111
And the connection is back.

UseDNSNameForDiscoveredNodes = 1

Try to do configuration poll for the node with changed IP address - will it resolve primary host name to new IP?

Best regards,
Victor

I did that already but no change. (configuration, status poll...

I have noticed that sync with dns did not worked for server node only.