Proper Environment Setup

Discussion in 'Installation/Configuration' started by fishtenors, Sep 27, 2007.

  1. fishtenors

    fishtenors New Member

    Can someone please help me with some basic concepts? Here is what I'm working with. I've got 3 servers here at my office, I have a block of 5 static IP addresses issued by my ISP, and I've got a Linksys router. My current set up is this:

    All 3 servers are behind my Linksys router. The router is using one of the issued IP addresses, well say it's (my block is thru On said Linksys router, I have setup port forwarding for ports 21, 25, 80, 110, etc. The usual ports. Those ports are forwarded to Server B (yes server B) at

    Server A is a Mac G5 Xserve. Very powerful, and very capable of handling several different tasks. At present it serves only as a file server. Wasteful, I know, but please read on.

    Server B was never meant to be a solution, but merely a band-aid. It is a 600mhz, 128mb ram, 100gb hdd, old Gateway desktop machine running Fedora 6 and ISPConfig. It was set up to the exact (and I mean exact) specifications in falko's 'The Perfect Server - Fedora 6' (I love you falko). Server B just cannot handle the volume of traffic coming through our office.

    Server C is a descent machine, set up to to the exact (and, again, I mean exact) specifications in falko's 'The Perfect Server - Fedora 7' (I love you even more falko). Server C is waiting for glory, doing nothing, but ready for action.

    Here is my predicament. Server B is choking, and needs to have some of the load taken off, and the Linksys router can't handle the traffic either. Here is what I was thinking as a solution: I would like to move the router to a new IP,, assign one of the NIC cards on Server A the public IP of The other NIC on Server A would be assigned, so it could still communicate with the other machines on our internal network (for file sharing and....)

    Here is the catch. I have 7 domains. All point to our public IP via off-site DNS. I'm hoping that I can configure Server A to 'route' traffic to the appropriate server on our internal network. For example, and would live on Server A, thru would live on Server C, and would live on Server B (that's about all it could handle).

    Here's a scenario: someone wants to visit They type it in their browser, GoDaddy points them to our public IP, Server A accepts the request as it has a DNS entry for the domain, and finally sends the person along to Server C at

    My question: does this make sense? Is this how it's done out there in the real world? I have no professional training, so I apologize if I sound like an idiot. But I'm really interested in learning, and this site has been an extremely helpful outlet of knowledge for me. Also, please let me know if this is in the wrong forum. Thanks.
  2. falko

    falko Super Moderator ISPConfig Developer

    Normally you'd configure your router (server A) to forward port 80 (for http) to another backend server. The problem is that you cannot forward a port to more than one backend server, so this would not work for you...

Share This Page