Interesting problem needs interesting solution

[crenn]

I have a couple of home servers and I want to set up alias based port forwarding. IE if I access party.example.com on port 443 it shows https from server 1 but if I access hard.example.com on port 443 it accesses SSH on server 2.

[jdbnsn]

why not just route them by DNS?

[x88x]

Is this accessing them from an external location? If so, what DNS service are you using? Do you have a static or dynamic IP address? Are any of the servers publicly accessible?

Barring any of that changing things, what I would do is set up a VM with the necessary ports open to the world, then have it handle routing stuff depending on what you want it to do.

[crenn]

I'm using DynDNS. I have a single static IP address, and the servers are publically accessable currently. Why can't I just get the linux router which I'm using to port forward to handle what I want to do?

[x88x]

You might be able to, it all depends on the capabilities of your router. I'm actually not sure off the top of my head how to do it, but I'll think on it.

[crenn]

Either way, if it can't be done linux based, then I'm not sure how to do it at all.

EDIT: By the way, apache can do virtual hosts, but sadly the way to get things work with SSH is to use a tunnel which I don't want to do.