If your server isn't behind a dedicated firewall machine, when you're on a 
dynamic IP, then you reap what you sow, in all fairness.

And if you're on a dynamic IP, you'll have to worry about updating the DNS 
for every domain every time it changes.

So, the short answer is to make sure that your server is behind a firewall 
of some sort.  Then, you assign a private IP address to the server, 
itself, and use that IP in your httpd.conf file.

However, the fact of the matter is that you can not use the wildcard * for 
each of the virtual domains.

That's exactly how I do it.

On Sun, 21 Sep 2003, Lorenzo Prince wrote:

> Mike Burger staggered into view and mumbled:
> > You can't use "<Virtualhost *>".  Instead, you will have to use 
> > "<VirtualHost xxx.xxx.xxx.xxx>" where "xxx.xxx.xxx.xxx" is the IP address 
> 
> But what do I do if I have a dynamic IP address?  It wouldn't be practical to change 
> the IP address in httpd.conf every 
> time my IP changes, ad if I did that I may be down for a day or more before I 
> realized my server wasn't listening 
> properly.
> 
> Prince
> 
> 
> 

-- 
Mike Burger
http://www.bubbanfriends.org

Visit the Dog Pound II BBS
telnet://dogpound2.citadel.org or http://dogpound2.citadel.org:2000

To be notified of updates to the web site, send a message to:

[EMAIL PROTECTED]

with a message of: 

subscribe


-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list

Reply via email to