0

Hy everyone, I'm not a networking newbie, but a 'stackoverflow' newbie for sure, so I apologize in advice if i screwed-up category or group, but there seems that all this stuff is based on tags.

I have the following question that crossed my mind as I'm expanding my test server.

  • I worked with WWW balancing (Having different public IPs referred to the same domain)
  • I worked with internal hardware balancers (with traffic comming from same public IP and a single url www.example.com)

But this morning I got two new machines from a friend, and I decided that will keep them for my selve expanding my testing server from 1 to 3 units.

Now , as I have few domains, a public static IP and a fast connection (FTTH) that is enough. I was wonderding to have someones opinion, that may allready did it and therefore figured out the best solution.My domains refer all to the same IP and my routher has just a DMZ server option that forward traffic to a single LAN IP.

Now which are the solutions (rather hardware) that allow me to split ingoing HTTP/HTTPS request according their URL?

www.example.com -> server01 [10.10.0.1]

ftp.example.com -> server02 [10.10.0.2]

Newbie
  • 113

2 Answers2

0

If you insist on hardware, I'd suggest Cisco ACE or something similair.

But it's an incredible waste of money. For the fraction of Cisco's junk's cost (and yes, Cisco ACE is junk), you can deploy a Linux server running Apache, Nginx, Varnish or whatever, that will do everything you need and more.

0

PFSense can do it. There's no point in buying some kind of appliance to do it, it's mostly the same thing and way cheaper. Linux could do it too, the same way.

Having two subdomains on one public IP addres behind pFsense router