Problem with DynamicDNS and SSH or Sever PART1 - theory.

Hi, just a two months ago I started a new company, offering new and innovative type of services "Remote office assistant" . Early in the begining I`ve got an Idea to set up a server in my as a base, situated in my office.
At first stage brilliant idea - have server, switch it on, install LINUX and let`s go.

Hey guys not so easy, my ISP company offered only Dynamic DNS support or (as they said) almost impossible to jump to static IP, except to pay 10 times more a month. OK, that was not a solution, but I did not gave up, after some research and road back to theory I found out:

• First, what says definition of Dynamic DNS - DNS is a method, protocol, or network service that provides the capability for a networked device, such as a router or computer system using the Internet Protocol Suite, to notify a domain name server to change, in real time (ad-hoc) the active DNS configuration of its configured host names, addresses or other information stored in DNS. A popular application of dynamic DNS is to provide a residential user's Internet gateway that has a variable, often changing, IP address with a well known host name resolvable by network applications through standard DNS queries;


• Second - Conclusion from theory, this is something that changes, not static, so almost impossible to assign to server or even desktop, if you want your deals with ssh and network based solutions;


• Third - once again back to theory now lets see functions. The user of DNS may be supplied with a different IP address every time an Internet connection to the service provider is made, so there is no stable address to connect to. If a DDNS service is used to associate a fixed address to a device, then the user can, for example, establish a Virtual Private Network (VPN) to the network using that address. As a detailed example, the IP address can be 123.234.111.112 one day, 123.124.45.15 the next, but the DDNS address will always be, say, myhome.ddns.org. A remote control program such as VNC server can be left running on a machine in the network; the user can connect to the network by establishing a password-protected VPN to myhome.ddns.org, then connect to the machine using a VNC client program;


• Fourth - last. So From this we need a some third party service provider, who can assign an domain to may always changing IP addresses.

I`ve finnished with my theory, inspired from wikipedia article , thats it for today. I will continue with practical issues soon on PART2.