Actually, Apache will let you set up virtual hosts either way - all using the same IP on a single box, or you can setup Linux to respond to multiple IP addresses on the same box, and then tell Apache to direct based upon the destination IP address. We've run both ways over the years, however given that you're sitting behind a firewall, I would suspect that preservation of IP addresses is an issue. In that case simply use the single IP address virtual hosting capability.
You might also want to check out the Apache documentation on this at: http://www.apache.org/docs/vhosts/ Best Regards, Tim Kehres International Messaging Associates http://www.ima.com ----- Original Message ----- From: "John Nichel" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, January 02, 2003 4:43 AM Subject: Re: Apache VirtualHost to another machine > Assuming the IP for the second box can be hit from the outside, yes. > However, this doesn't involve Apache. Virtual hosting allows you to > serve up multiple domains from the same box. Those domains don't need > to have different IP's, but they have to be on the same box for Apache > to serve them up. Technically, you could do a samba mount to the other > box, and point the virtual host to the mount point, but why? > > Jonathan M. Slivko wrote: > > Can't something be done with some tricky DNS routing as well as > > <VirtualHost *> (assuming there is only 1 domain on this server)? > > > > -- Jonathan > > > > -- > > Jonathan M Slivko <[EMAIL PROTECTED]> > > Website: http://www.speakeasy.net/~jslivko/ > > "In God We Trust, All Others Pay Cash!" > > > >> From: John Nichel <[EMAIL PROTECTED]> > >> Reply-To: [EMAIL PROTECTED] > >> To: [EMAIL PROTECTED] > >> Subject: Re: Apache VirtualHost to another machine > >> Date: Wed, 01 Jan 2003 14:28:23 -0600 > >> > >> Let me make sure I understand you. You have a static IP address for > >> one machine on your network. On that machine, you have Apache running > >> a domain. Also on your network, you have a seond machine, also > >> running apache, serving up a second domain. You're pointing the DNS > >> for both domains to the first box with the static IP, and trying to > >> use the Apache virtual host directive on the first box to server up > >> the domain on both that box, and on the second box? > >> > >> I haven't played around with Apache2 yet, but I know this isn't > >> possible with 1.3x versions. The virtual hosts must be on the same > >> box. What kind of IP does the second box have? Static, dynamic, > >> something you made up for your internal network? For Apache to serve > >> up the second domain, you need to point the DNS to that second box (if > >> it has an IP that can be hit from the outside). > >> > >> > ps - this experience is the only one I've had with Apache that makes > >> > me miss a feature of IIS. > >> > >> I've never used IIS, but I'd be suprised if it would point a virtual > >> host to another box. > >> > >> Brad Alpert wrote: > >> > >>> 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. > >>> > >>> > >>> > >>> > >> > >> > >> -- > >> By-Tor.com > >> It's all about the Rush > >> http://www.by-tor.com > >> > >> > >> > >> -- > >> redhat-list mailing list > >> unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe > >> https://listman.redhat.com/mailman/listinfo/redhat-list > > > > > > > > _________________________________________________________________ > > STOP MORE SPAM with the new MSN 8 and get 2 months FREE* > > http://join.msn.com/?page=features/junkmail > > > > > > > > > -- > By-Tor.com > It's all about the Rush > http://www.by-tor.com > > > > -- > redhat-list mailing list > unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe > https://listman.redhat.com/mailman/listinfo/redhat-list > > -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
