After days of fruitless travail trying to get this working, I am
asking for help before I lose my will to live :)

I have an external IP registered in DNS.  The machine that hosts
apache 2.040 is publicly accessible and everything with it works
fine.

Here's the problem:

I have another machine inside the firewall which is running apache. 
I have a another registered domain which I want to serve from this
machine.  I thought that the name-based VirtualHost directive would
do the trick, but when I add the VirtualHost section (listening on
the same port as the main site) along with ServerName, etc., an
external access to www.insidedomain.com opens the
www.outsidedomain.com page.

I have tried ProxyPass, PermanentRedirect, a combination of name-
and IP-based virtual hosts, anything I could think of, but nothing
works.

DNS is right, so far as I can tell; the internal and external
entries are there (split-brain).  An external ping to
www.insidedomain.com results in a hit, as expected.  The
www.insidedomain.com site is accessible from inside the network. 
But any attempt to access it from outside fails over to the default
virtual (main) site.

So, the short question is - is anybody successfully running, on a
single external IP, a virtual host inside the same internal network
that is accessible from outside by that virtual site's registered
name?  If so, any tips would be greatly appreciated.

I could post the VirtualHost sections from my httpd.conf, but
frankly it has gone through so many iterations that it would be
pointless.  What I need is a working example or at least a pointer
on the right approach to take.

Any help much appreciated!

Thanks/Brad

ps - this experience is the only one I've had with Apache that makes
me miss a feature of IIS.




-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to