[Thinlinc-technical] Split horizon DNS

Rob Evans rob.evans at originvs.com
Fri May 4 16:18:06 CEST 2018


Use a hostname in VSM rather than an IP and then create a local DNS a record resolve this internally.

E.g. tlinc01.somehost.com =

Public =

Local IP

Also maybe edit the hosts file and add the FQDN name pointing at the local IP of the ThinLinc box.

Should then work great either from WAN or LAN


* Sent from my mobile device *

On Fri, May 4, 2018 at 3:08 PM +0100, "Jonathan Buzzard" <jonathan.buzzard at strath.ac.uk<mailto:jonathan.buzzard at strath.ac.uk>> wrote:

I am struggling to get thinlinc running on a new setup, and the
complete lack of data being dumped into the log files does not help.

Basically at the client I am getting "
 The SSH connection succeeded, but the ThinLinc server connection
failed.Perhaps this server doesn't run a ThinLinc server?"

The VSM server is however running. I am in fact entering the correct

However B.2.1.3 says "In very rare cases, this could also be caused by
incorrect DNS data." This leaves me wondering if split horizon DNS for
both the vsm server and vsm agent machines is causing a problem?

That is if I as the client look up the hostname of the either the
server or agent I get a different IP address than server and agent get
when looking up each other. That is the client gets the public IP
address and the vsm server/agent get their internal private IP address.


Jonathan A. Buzzard                         Tel: +44141-5483420
HPC System Administrator, ARCHIE-WeSt.
University of Strathclyde, John Anderson Building, Glasgow. G4 0NG

Thinlinc-technical mailing list
Thinlinc-technical at lists.cendio.se
Manage your subscription:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cendio.se/pipermail/thinlinc-technical/attachments/20180504/e66ebfed/attachment.html>

More information about the Thinlinc-technical mailing list