Re: [users@httpd] Virtual host causing problems with default server

[Robert Moskowitz <rg...@htt-consult.com>]

At 03:45 PM 7/10/2003 +0200, Robert Andersson wrote:

>Is home.com defined as a virtual host? If that is your "main server" and it
>isn't sitting on a different IP than your virtual hosts, you won't ever
>reach, due to reasons previously explained. If you are using name-based
>virtual hosting, you must define each site/domain as a virtual host. With a
>few exceptions, once you start adding virtual hosts, your "main
>configuration" only becomes the default configuration for the virtual hosts;
>not a host of its own.
>
>If you still have problems, please summarize your case again, since this has
>become a bit confusing.

Boy, was I confusicated by the docs that I read.  Thanks to a doc sent to 
me by Patrick Donker, I figured out all I was doing wrong....

Both the NameVirtualHost and the <VirtualHost _____> are suppose to have IP 
addresses for the server, and only FQDNs if you want to use DNS at startup 
to resolve names to addresses.  Dah.

What distinguishes multiple <VirtualHost _______> blocks is the content of 
the ServerName entry.  This was not clear from the main VirtualHost doc 
page, their it seemed like you needed separate IP addresses for each 
virtual host (which was once the case).

So it is working now.  I have my NameVirtualHost entry and 3 <VirtualHost 
_____> blocks.

thanks all!


The only person who always got his work done by Friday was Robinson Crusoe.


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org