Connection Timeout during Ansys Remote Solve result retrieval

DNS Resolution and Gateway Communication

Ansys Remote Solve utilizes a Gateway server to broker the connection between the local client and the compute cluster. While the job may successfully submit and execute on the cluster, the process often fails during the phase where results are returned to the client.

The system relies on the compute nodes being able to resolve the client's hostname to establish a return path. In environments where the client and cluster reside on different subnets, the behavior of DNS suffix search lists can lead to resolution failures, resulting in a connection timeout.

Given this architecture, how does the Ansys Gateway handle hostname resolution when the client is identified by a short-name that is not globally resolvable across subnets? What is the documented mechanism for ensuring the compute node can resolve the client's identity without modifying the global DNS search suffix?