|
Home > Archive > Web Servers on Unix and Linux > June 2004 > Apache virtual hosting and name resoution
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Apache virtual hosting and name resoution
|
|
|
| We provide shared hosting for about 100 domains on LAMP servers. All
these servers are behind a firewall which runs an internal DNS, which
in turn helps these web servers resolve the domains hosted on each
machine. Now, I want to get rid of this internal DNS but the only way
I can do it by filling up the hosts file on each server. Is there any
other way of addressing this situation?
--Turi
| |
| Steven J Sobol 2004-06-08, 12:03 am |
| Turi <adityai@hotmail.com> wrote:
> We provide shared hosting for about 100 domains on LAMP servers. All
> these servers are behind a firewall which runs an internal DNS, which
> in turn helps these web servers resolve the domains hosted on each
> machine. Now, I want to get rid of this internal DNS but the only way
> I can do it by filling up the hosts file on each server. Is there any
> other way of addressing this situation?
How many servers? (Servers, not individual sites)
--
JustThe.net Internet & New Media Services, http://JustThe.net/
Steven J. Sobol, Geek In Charge / 888.480.4NET (4638) / sjsobol@JustThe.net
PGP Key available from your friendly local key server (0xE3AE35ED)
Apple Valley, California Nothing scares me anymore. I have three kids.
| |
|
| Steven J Sobol <sjsobol@JustThe.net> wrote in message news:<3_6dnafe_eIBn1jdRVn-hw@lmi.net>...
> Turi <adityai@hotmail.com> wrote:
>
> How many servers? (Servers, not individual sites)
We have three.
--Turi
| |
| David Efflandt 2004-06-09, 8:33 am |
| On 7 Jun 2004 14:40:31 -0700, Turi <adityai@hotmail.com> wrote:
> We provide shared hosting for about 100 domains on LAMP servers. All
> these servers are behind a firewall which runs an internal DNS, which
> in turn helps these web servers resolve the domains hosted on each
> machine. Now, I want to get rid of this internal DNS but the only way
> I can do it by filling up the hosts file on each server. Is there any
> other way of addressing this situation?
If the IP the names resolve to is not on the server, you can use wildcard
("*") NameVirtualHost * and <VirtualHost *> sections. Then the IP will be
ignored and apache will just pay attention to ServerName or ServerAlias
for each wildcard vhost based on Host header from browser. IP based
vhosts still work for specific IPs like <VirtualHost 127.0.0.1>, since
IP based hosts are considered before wildcards (likewise ServerName
this-host.some.domain is considered before another vhost with ServerAlias
*.some.domain).
--
David Efflandt - All spam ignored http://www.de-srv.com/
| |
|
| efflandt@xnet.com (David Efflandt) wrote in message news:<slrncccoae.o3t.efflandt@typhoon.xnet.com>...
> On 7 Jun 2004 14:40:31 -0700, Turi <adityai@hotmail.com> wrote:
>
> If the IP the names resolve to is not on the server, you can use wildcard
> ("*") NameVirtualHost * and <VirtualHost *> sections. Then the IP will be
> ignored and apache will just pay attention to ServerName or ServerAlias
> for each wildcard vhost based on Host header from browser. IP based
> vhosts still work for specific IPs like <VirtualHost 127.0.0.1>, since
> IP based hosts are considered before wildcards (likewise ServerName
> this-host.some.domain is considered before another vhost with ServerAlias
> *.some.domain).
I don't think this addresses the issue of SSL. There are few sites
that have to have dedicated IP for SSL. Am I confusing myself?
--Turi
|
|
|
|
|