httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joshua Slive <>
Subject Re: [users@httpd] IP Aliasing & Virtual Hosting issue w/ Apache 2.0.48
Date Fri, 26 Dec 2003 04:32:49 GMT

On Thu, 25 Dec 2003, David wrote:

>     Listen
>     Listen
> <Virtualhost>
>     servername
>     serveralias, *
> </Virtualhost>
> <Virtualhost>
>     servername
>     serveralias, *
> </Virtualhost>

This is basically correct, except that the ServerAlias lines don't do
anything.  They are only relevant in the case of name-based virtual hosts.

> I intended have nothing listed for the Documentroot, since is only the
> configuration phase, and it defaults the Apache documentation page.

You should put a DocumentRoot in both vhosts, even if it is the same as
the main server DocumentRoot.

> I get successfully retrievet the default Apache page for DOMAIN1.  VIA its
> local address, as well as outside the LAN.  But thus far haven't had any
> success "seeing" my DOMAIN2 internally or otherwise.
> Does IP Aliasing require that another "network" address be used?  (ie.
> &


> I suspect my issue lies within the IP
> Aliasing.
> I can successful ping the IP Alias address locally. And
> netstat reveals that both addresses/port are up & listening.

>From the server, try
telnet 8080
GET / HTTP/1.0

If that gives you the page, then apache is working fine.  Try the same
thing again from another machine on the LAN to see if it is a networking


The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message