Discovery assigns DNS names to nodes, not addresses

Started by pvo, January 11, 2021, 12:35:00 AM

Previous topic - Next topic

pvo

My server property UseDNSNameForDiscoveredNodes has the value 0  but the Nodes accessible via Zone proxy running on Amazon VPS receive the name like "ip-192-168-213-2.eu-central-1.compute.internal" as the Object name. This name is probably some internal Amazon DNS name.
On Zone proxies which are not running on Amazon VPS the IP address is assigned but there are no such DNS names available.

Is the property UseDNSNameForDiscoveredNodes not working on proxies or did I understand something wrong?

Victor Kirhenshtein

Hi,

UseDNSNameForDiscoveredNodes controls assignment of primary host name (DNS name or address used for communications), not node name (the one you see in object tree, etc.). Resolving node names from IP address is controlled by Objects.Nodes.ResolveNames.

Best regards,
Victor

pvo

Thank you.
According description this setting is common for DNS and SNMP system name. Is it possible to assign SNMP name only or change the name assigned by DNS if the SNMP agent is enabled later?

Victor Kirhenshtein

It is not possible to configure server to use only SNMP sysName for resolving node name. However, you can synchronize node name with SNMP sysName by adding the following code to configuration poll hook script:


if (($node != null) && $node->isSNMP && ($node->name != $node->snmpSysName))
{
$node->rename($node->snmpSysName);
}


It will update node name according to SNMP sysName on each configuration poll.

Best regards,
Victor