Idea ID 2777833
the current mechanism of the Host Connection job to discover the node's primaryDnsName attribute is based on the "smallest IP".
assuming a server has following 2 ip addresses / dns names:
- 126.96.36.199 / servername-backup.domain.com
- 188.8.131.52 / servername.domain.com
as a result the node's primaryDnsName attribute would be set as "servername-backup.domain.com".
so far, at every customer I have been to this is not what they would see as the correct primary dns name.
my suggestion instead is to run the hostname command and resolve the dns name from it.
at the same time this could be used to set the node's primaryIpAddress (this attribute is currently not discovered by Host Connection by Shell job. here is another idea for this: https://community.microfocus.com/t5/CMS-Idea-Exchange/Discover-the-primary-IP-address-by-the-host-connection-job/idi-p/1663340).
I would be also glad to hear other opinion's about the "smallest IP" mechanism and if there are good use cases for it.
I could also imagine a new job parameter where discovery admins can decide whether to use the smallest IP mechanism or the hostname command to discover primaryDnsName / IP.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.