Hi,
The way I do it to have a server available about 20 hours a day with dynamic IP:
#1. Register for a dynamic domain (Dynamic DNS), e.g.
I am using one of there alternative Domain Suffix for my home computer, i.e. flyinggorillaz.homeip.net.
#2. Install one of their Client programs for Windows, e.g. DirectUpdate (Shareware).
What this does. DYNDNS allows an IP address to be bound to a frequently changing IP address. DirectUpdate (or similar tool) then uses a specific protocol to update your account with DYNDNS with your new IP address. When installed as a Windows Service, it recoginises a new IP (e.g. when I dial my DSL modem) and updates your domain.
That should now work without any other config changes within Apache.
However, as I have sub domains that I wish to serve as seperate web sites, I use Virtual Hosts in Apache to have capture alternative requests and route them to different DocumentRoots etc.
To do this with dynamic IPs, you must configure Apache to use Named Virtual Hosts.
My virtual hosts recieve requests on:
#1. [tt]
[/tt]
[This is an empty web site - mainly to test virtual hosts]
#2. [tt]
[/tt]
#2 actually uses the RewriteEngine to redirect all ROOT requests to the WebApp "JetSpeed". So any my.flyinggorillaz requests are routed to a portal server.
I have other domains routed to a friends server - but we haven't yet installed the virtual hosting, so
goes to his Default HTTP Server!
If you have further questions, please let me know!
Good luck,
Phil