Cluster Access outside main Domain via Job Manager

#### Problem Description
The cluster is part of DomainA and its head node has the full DNS path of headnode.domaina.com. A user that is part of DomainB and attempting to use the cluster from a computer in DomainB, is unable to use the cluster without updating their local hosts file. This appears to be because the cluster is returning the active head node as "headnode" instead of "headnode.domaina.com". This was not an issue in HPC Pack 2012 but appears to be in HPC Pack 2019.

#### Steps to Reproduce
Attempt to connect to an existing cluster from outside the cluster's domain with an account from a different domain.

#### Expected Results
Successful connection.

#### Actual Results
Failure to identify the head node and an unsuccessful connection.

#### Workaround
Specify the full DNS path of the head node in the user's hosts file.

Start by reproducing the cross-domain connection described in the issue and examine how the active head node is returned to a user in another domain. Done means the cluster can be identified and connected to successfully without requiring a local hosts-file entry.

Written by the indexing model from the issue text.