New: A DNS server can be marked Global DNS server, which makes the asset the system-wide resolver of the connected client instead of answering only for assigned domains. The option is offered while the server has no domains; the resolver the device used before connecting is kept behind the asset as a fallback.
Agents
New: DNS assignments are now applied on Linux clients. Both per-domain DNS servers and the new Global DNS server option are honoured, on machines using systemd-resolved, resolvconf, dnsmasq (OpenWrt, RutOS) or a plain /etc/resolv.conf. On a gateway, the assigned asset also becomes the resolver for the devices behind it.
New: The Global DNS server option is applied on Windows, macOS and Linux clients.
New: xtna-launcher accepts -ignore-hostname, so a container installation no longer registers with its container ID as the asset name.
Fixed: On Windows, a tunnel service left half-registered by an interrupted installation kept the client from connecting, and reported a driver problem instead of the actual cause. Such a registration is now repaired on the next start.
Fixed: On Windows gateway assets, a client joining or leaving a policy dropped every established connection through the gateway, ending long-lived sessions such as SMB.
Fixed: The desktop client gave no sign when it could not reach the agent service. It looked healthy, accepted input that never took effect, and wrote large amounts of repeated messages to its log. It now shows a warning while the service is unreachable, and clears it as soon as the service is back.
Fixed: On Linux, the desktop client could not reach the agent service after installation, and logging out and back in did not help.