Most people seem to have missed a critical part of the first post:
QUOTE (x-Shadow-x @ Oct 3 2008, 08:42 PM)

And how would I link it to my home server?
Unless you're on a static IP (most ISPs charge extra for that), then using a plain old domain name will mean downtime every time your IP changes (for you to realize it stopped working, then updating it, and changes to propagate).
For those type of scenarios, there's really only 1 solution: DynDNS's custom DNS service (perhaps others have a similar service, I never actually looked). Your DynDNS client app will make it update the IP "instantly" (just like for any usual DynDNS entry), with no downtime.
I never personally bothered, as my up speed sucks way too bad for any practical "server" use (0.9mbit). And to VPN in and such, a plain old DynDNS entry works just as well (no harder to remember than whatever long domain name you can come up with these days -- pretty much anything you can think of is already taken).