The problem with this services is that it only gives you a subdomain, like server.dyndns.org. What if you want to run a couple of virtual hosts in apache at your home server? You would need to pay this free services a fee, so that you could use your own top level domain, like something.com.

Well, if you already have a domain, and have a control panel to edit the DNS entries of it (if you don’t have a control panel, you should, so change your registrar), you could create as many subdomains as you want, and pointing them with a CNAME to the subdomain you created on dyndns or no-ip.

This way, your real subdomains are always up to date with the correct ip of your home server.

To recap:

On dyndns, create a domain: server.dyndns.org

On your domain control panel for something.com, create a subdomain server.something.com and point it with a CNAME registry to server.dyndns.org.

Now, when you use server.something.com, you will be redirected to your home server. If you have different subdomains on something.com pointing to the dyndns subdomain, you can control on apache which websites will be active for each subdomain using virtual hosts.

Hope this was usefull for all of you