Inbound web page routing

[3D0G]

Greetings:

I have a single static IP address. I just added a new PC running Apache to my internal LAN so now I have both an IIS server located on x.x.x.2 and the new Linux webserver on x.x.x.3

Web traffic (port 80) coming to my domain (lets call it foo.com) is routed to the IIS server on x.x.x.2

What I need to do is route traffic coming to a specific subdomain like new.foo.com to the apache server on x.x.x.3 and let all other port 80 traffic continue on it's merry way to the IIS sever on x.x.x.2

Any chance my Actiontec router can do that?

3D0G.

 

[zx10guy]

When you say static are you talking about an ISP provided static IP or are you talking about private internal addresses?

 

[3D0G]

ISP provided static.

I know I can use port level forwarding to route inbound traffic but in this case I want port 80 traffic to go to one of two diffrent computers based on the URL being requested.

 

[JohnWill]

I'm not sure how you'd do that. Since you only have one IP address, and you can only forward port 80 to a single computer behind your router/firewall, that seems like the impossible dream.

 

[zx10guy]

You can do this but you'll have to ditch the router you have. I don't know what other network devices do this but I know for a fact the Cisco PIX and ASA firewalls can do this. You just set up a static NAT rule for the second public IP you have and then set your firewall rule to only allow inbound port 80 on that IP. Not sure what your budget is for this...if it's even an option. But you're looking at spending around $370 for an ASA 5505.

 

[JohnWill]

The only way I've seen this done is by using an external service that translates one or more ports from port 80 to a unique port. Also, I don't see anything here that suggests he has multiple public IP addresses, which is the root of the issue if that's correct.

 

[zx10guy]

Trust me. What I said works because I implemented it myself. Numerous times on various work projects.

As far as the question of ISP public static addresses. The OP said it in post #3.

ISP provided static.

 

[JohnWill]

As far as the question of ISP public static addresses. The OP said it in post #3.

I must have flunked reading comprehension, I don't see anything about multiple public IP addresses there, just a statement about the IP address being static. Please point out what I'm missing?

 

[zx10guy]

I must have flunked reading comprehension, I don't see anything about multiple public IP addresses there, just a statement about the IP address being static. Please point out what I'm missing?

Nope, I flunked reading comprehension. Guess that's what I get for doing multiple things at once when responding. I saw in his first post he said he had a singlet static. Oh well, I retract all I've said.

 

[3D0G]

Oh well, I retract all I've said.

Drat. I was hoping I was just missing that option in the feature list.

OK then, it's back to plan-B. I'll just have to point the URL at another outside server and have it forward the request back to foo.com:81.

Thanks All.

 

[JohnWill]

That would be the only way I see this working.

 

[zx10guy]

dyndns.com offers a free HTTP forwarder.

 

[JohnWill]

dyndns.com offers a free HTTP forwarder.

See Post #6.