Overview

Following feature enables that Terminal Professional can connect YSoft SafeQ server via hostname or Fully Quallified Domain Name (FQDN).

Note: When host names are set then they are overriding and also replacing setting of server IP and other server node list (values of configuration items SERVERIP and SERVERLIST).

Connection is made by this steps:

Terminal resolve all given host names via DNS server
Terminal according to results updates fields SERVERIP and SERVERLIST (primary server and other nodes list)
Connection negotiation to servers starts in usual way
If terminal is connected to cluster and receives new server nodes IP list then "SERVER_HOSTS", "SERVERIP" and "SERVERLIST" are updated according to settings (this may clear host names list).

Note: After bootup there is connect to server to inform it about new firmware version etc. This first connect is made according to value of "SERVERIP" not "SERVER_HOSTS" so no resolving is made. This will ensure to connect to server from which the update was made.

Configuration

Service menu

In service menu level 1 there are these options:

Server settings -> Server hostnames
- Allows to enter list of server host names in format like "hostname1:port hostname2:port"
- Host name could be any valid DNS name like "sqsrv.company.local"
- When server hostname is set, the setting of server IP and port are disabled. To enable them you have to clear server host names.
Server settings -> Clear srv hostnames
- Clear server host names setting

Current related options:

Server settings -> Refresh server IPs
- Automatically - After successful connect to SafeQ cluster, the existing host names list is replaced by new Server IP list obtained from cluster node (Host name list is cleared, SERVERIP and SERVERLIST are updated)
- Disabled - Setting of server host names is left unchanged

Remote configuration

The remote configuration can be performed via Remote configuration tool for hardware terminals

Configuration value of server host names is "SERVER_HOSTS". Reading or writing is supported with remote configuration tool via authorized access - pin for level 1.

Current related items:

SERVERIP - Primary server IP address and port in format like "10.0.0.1:4096"
SERVERLIST - List of IPs of other nodes of cluster like "10.0.0.2 10.0.0.3 10.0.0.4"

Limitations

In "SERVER_HOSTS" all ports has to be same (by default 4096)
Currently DNS resolving is not cached
Remote setting of "SERVER_HOSTS" is not propagated via resolving to "SERVERIP" and "SERVERLIST"
Static network configuration supports only one DNS server