NPM do not handle DNS name resolution when ConfigWizard run.
This process create entries in the "Orion Servers", Websites", and "Engines" tables (to name few) with no FQDN, so I have to edit the table and append the suffix manually.
We are forced to use the URLs with FQDN, otherwise, the links referring to nodes, components, etc. in the alerts will not work.
This also affects NCM with a message indicating that polling engine cannot communicate, and after I change the database entries I get a message saying “Identity check failed for outgoing message. The expected DNS identity of the remote endpoint was 'myserver.domain01.net' but the remote endpoint provided DNS claim 'myserver'. If this is a legitimate remote endpoint, you can fix the problem by explicitly specifying DNS identity 'myserver' as the Identity property of Endpoint Address when creating channel proxy". Solarwinds support can refer to Case # - 00104807 Jobs failing.
This screenshot is without FQDN.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.