Multiple web servers from one IP

[hd2]

Hello.

For years, I have been hosting about 24 web sites off an IIS NT4 (then later 2K server) machine on my cable connection, using simple host headers to allow multiple web sites from one IP.

Now, I have the opportunity to move my web server to a much faster, dedicated connection in downtown Toronto.
The problem is, there is already one web server at the Toronto location, and they only have 1 IP address.

I have installed RedHat 7.3 on another machine here, in the hopes that I could use it as a kind of 're-director' (for lack of a better word), that would look at the web page requests coming in, then direct the request to either 192.168.0.1 (server 1), or 192.168.0.2 (Server 2) depending on the web page address requested.

Thanks for any help or hints in the right direction.

Take care

 

[jvdboom]

Do you have a domain name(s)? there is something called No-Ip to stick a Ip to a (sub)domain if you can install router software on your linux-computer and set for example port 80 to server1 and port 8080 to server 2
you have to include the portadress in the Ip maybe you can get your yourdomain.com setted to 192.168.0.2

it seems that you already installed something like a router (the 192.168.***.*** address) ,(if you setted those servers to obtain automaticly a IP)

It is also possible to install another webserver on that computer and based on the refferer you can write a script that redirect it to the other servers

 

[hd2]

Hey, thanks for the reply.

I'm playing with Apache on the Linux box right now, hoping that I might be able to use the Virtual Host options in it to forward traffic to the correct servers on the sub-net.

Thanks again.
Take care

 

[hd2]

Here's an image that might help explain what I mean a bit better:

http://www.axsstudios.com/example.gif

A user on the web requests

http://www.y.com,

which resolves to 24.150.231.125

The linux box looks at the incoming request, sees that the user wants

http://www.y.com,

knowes that

http://www.y.com

is hosted on server 2, so it directs th request to 192.168.0.2

 

[hd2]

Thanks to everyone who reead this thrad.
I got it working.

Anyone who is interested in how, it was done using Apache's ProxyPass feature.

See this article:

http://www.linuxfocus.org/English/March2000/article147.html#lfindex1