trache

Chollman:

A friend of mine happens to work for that company, and gave me a basic idea of what happens if the update client stops unexpectedly:

Their servers update within minutes of the client going up and if your client isn't up, you get shunted to an "offline" page that tells the end user that "the current server you are trying to connect to is offline".

No matter what, everyone here would have seen /something/ regardless of whether or not your web server was listening for requests at the time. If they don't, that means your dynip client is active, but your web server is not (which imo is a no-no, since end users don't really know what's going on!).

By default, Apache listens to all of your network interfaces, including localhost. To test your installation, you can simply go to localhost via your browser. If it doesn't work, you should get an error page sent to your browser as well as an entry in your Apache access / error logs for you to peruse. In essence if it works locally, there's no reason it shouldn't work over the Internet (barring firewall rules of course).

__________________
"You looked at me as if I was eating runny eggs in slow motion." - Gord Downie of The Tragically Hip