I know this will be giberish to most of my friends…
if you have your own personal domain name; and decent router that supports ddns services, or a computer remains on most of the time, you could get something like:
DOMAIN: privatelan.lloydleung.com to point to your home LAN, and no longer a need to remember your IP while away from your network.
Say you wanted to connect to a device at home, and control it. You could now.
How would you like to be able to connect to your home network like: http://home.yourpersonaldomain.com and log into your personal webserver. Want another protocol instead of http, sure no problem.
- Sign up with a ddns service your router supports. Or if your technically savvy run a deamon/cronjob yourself.
- Set a cname on your dns that points to a ddns.
- if you don’t have access to your dns, contact your administrator, and they should be able to help you out on this.
- Setup on your computer or router update the ddns on the regular basis.
- I have a raspberry pi, which runs a cron job every 5 minutes, to connect and update my ddns provider.
- Create the port forwarding to the devices you want to go use.
- Such as HTTP, that would be port 80. The incoming port would be port 80, and you would forward it to an internal IP, say 10.0.0.101, on port 80. Save and apply these changes.
- When you connect to http://home.yourpersonaldomain.com it will now try and connect to your internal network machine that has the ip 10.0.0.101 on port 80.
So as an example, If I had a cname alias was “personalnetwork.lloydleung.com”, the ddns client will update the ddns server. On my router, I’d need to port forward whatever the application I was trying to go use. Some popular applications to use for this purpose would be RDP (port 3389), VNC (port 5900), ssh (port 22). How to setup these applications is outside the scope of this entry, and google is your friend.