User story #8022
Updated by Janos Mattyasovszky over 8 years ago
Determining how the node is called from "outside" is not always that easy, as it depends on many things: * Do *Do we use the same DNS Server as the policy server? * Do *Do we use the same IP to reach the policy server as the default gateway's IP's FQDN? (issue present on multi-homed servers) * Does *Does the external DNS also know me by the name I think I have? (SUSE's openstack assigns some bogus hostnames like external.server.fqdn) I would suggest to enable a "hook"-binary, that if it exists, it is executed to resolve the FQDN of the node being run on, since the sysadmin might have a better knowledge on how the nodes are named. Or it should at least be customizable via a local variable, but the binary-approach would actually allow you to use a custom logic to reilable resolve how the node is called, even if it is renamed.