gumb wrote:
On 08/09/16 18:29, Per Jessen wrote:
Yes - you could delegate your domain (example.com) to a dynamic DNS service and then create a record for "gumbssh.example.com". From the machine behind the NAT router, you would then update the DNS via their update script, typically over http. (just a script running curl or wget).
Ah, that's not really what I had in mind then. I have no idea how these things work, but I just saw that my own French ISP, free.fr, provides a reverse DNS configuration option so as to be able to use <domain name> as a shortcut to having to type in potentially variable numeric addresses in order to reach a machine on my own network.
The reverse map is not just a shortcut, it is needed for many things - mailservers and https for instance.
I thought that having the remote user's domain tied to their connection might similarly mean I could just SSH into their.domain.name and avoid any form of checking or updating for changes in their dynamic IP address.
With a dynamic address you can't avoid that. The DNS mappings don't change, i.e.: 1.2.3.4 -> 4.3.2.1.free.fr 4.3.2.1.free.fr -> 1.2.3.4 1.2.3.5 -> 5.3.2.1.free.fr 5.3.2.1.free.fr -> 1.2.3.5 But your mapping of "their.domain.name" to 1.2.3.4 or 1.2.3.5 will need to change when the IP address changes.
If it still requires a script, it's just as easy for me to ask the user to send me an email from their POP account each time I want to connect (or each time it fails to connect), and I can pick out the current IP address from there. Since they email me regularly anyway it's not worth getting into the hairies of scripts just for that.
If that works for you, that's good enough. FYI, the script is a one-liner - simply a "wget <url>". It's not a big deal or hairy in any way :-) -- Per Jessen, Zürich (16.7°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org