I'm thinking about getting SBC DSL service (dynamic IP), but I'd like to be able to log into one of my Linux boxes using SSH. I'm told that an effective (and cheap) alternative to static IP service is to use DynDNS. I was wondering if the following setup below will do what I want. AFAIK it should, but I'd like a second opinion before I shell out the $$$ for DSL service.
I'm planning on connecting my DSL modem directly into a router (e.g. Linksys), which will negotiate the PPoE connection with SBC (dynamic IP DSL service). Thus, the router will get an IP address from SBC's DHCP server. I plan to register a dynDNS domain name (e.g. foobar.dyndns.org) and have the router update dynDNS when the IP address changes (I'm told some linksys routers will do this). I plan to have my PCs sit on the other side of the router, which will each have 192.68.0. addresses. I will use NAT/IP Masquerading in the router to connect my PCs to the rest of the internet. So that I can SSH into one of my linux boxes, I will have the router forward any incoming traffic on the SSH port to my Linux box's IP address (e.g. 220.127.116.11). That way, I should be able to SSH to my dynDNS domain name, and connect to the correct Linux box.
If I should be doing something different, please let me know. If this is how you do it, I have the following questions:
- How long does it typically take for the dynDNS changes to propagate to other DNS servers? Is it on the order of minutes? hours? days?
- Are there any other complications with tunneling the SSH connections in terms of hostname authentication or anything else?
- Is SBC OK with me keeping long running SSH sessions running (e.g. on the order of days), provided they don't take up much bandwidth?
thanks in advance for your help, Matt