Internal network static IP, dyndns account connects to wrong home server
Hello,
If this is more of a server issue, please respond so that I can move it to the "server" section of the site.
Anyway, I've recently set up a dyndns account that connects to my home server on my network. I used a tutorial the other day that allowed me to set up a cronjob that would update dyndns ever so often.
Today, when I tried to connect to the server from school, the connection would not respond, and would eventually drop -- I figured that my server turned itself off, but this was not the case. I got home to find that my server had changed it's internal network IP from 192.168.0.2 to 192.168.0.3. SSH forwarding (from my router only goes to 192.168.0.3 now). I was wondering how it would be able for me to set up an internal static IP that goes from my router to my server (so that my server's IP never changes) and that my dyndns hostname will always make sure it connects to the server no matter what (because the internal network IP will always stay the same).
I was talking to a friend that told me that cronjobs are not responsible for a service that updates my router ever so often to tell it to forward port 22 to a different internal IP (the location of the server).
Any thoughts on this would be greatly appreciated! Thanks!
|