Dealing with roaming machines
martin f krafft
madduck at madduck.net
Wed Dec 24 00:51:11 EST 2014
also sprach Nico Kadel-Garcia <nkadel at gmail.com> [2014-12-23 07:50 +0100]:
> If it's not "in the local network", then it shouldn't get the
> subdomain of the internal network, and you've got a DNS "views" or
> DHCP configuration issue.
While the machine is not at the office, other machines can resolve
fishbowl.office to a valid IP… that's the same as resolving the
hostname of a machine that's turned off.
> I'm now assuming that you now have fully qualified hostnames that
> differ in each environment?
fishbowl.office → 192.168.17.33
fishbowl.home → 192.168.14.33
fishbowl.lab → 192.168.15.33
The three /24 networks are connected via a VPN. All three names
resolve to the appropriate IP, and obviously when at the office,
a request for "fishbowl" will yield 192.168.17.33 while it would
yield 192.168.14.33 at home (due to DNS search).
I'd kinda like OpenSSH to connect to all three IPs at once, since
only one will ever be answered at any one time. Or it should try
them in quick succession.
I realise that this is not really an OpenSSH question anymore and
I am sorry about that. The dynamic DNS solution is probably the
cleanest solution anyway. But the topic seems to have struck some
@martinkrafft | http://madduck.net/ | http://two.sentenc.es/
"the sick do not ask
if the hand that smoothes their pillow is pure,
nor the dying care
if the lips that touch their brow have known the kiss of sin."
-- oscar wilde
spamtraps: madduck.bogus at madduck.net
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 1107 bytes
Desc: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
More information about the openssh-unix-dev