Chris: Wouldn't multiple IP's on the External Interface with corresponding DNS entries be a lot more effective way to deal with this. Then each server could have an associated DNAT and FORWARD rule. Just a thought. I don't know what your limitations are.
Stu......... -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Antony Stone Sent: April 29, 2002 2:07 PM To: [EMAIL PROTECTED] Subject: Re: DNS Based Routing On Monday 29 April 2002 9:55 pm, Chris Hoeschen wrote: > I was wondering it there was a way to route HTTP request for abc.com to one > box and xyz.com to a different box if both abc.com and xyz.com resolve to > the same IP address. No. Routing is an IP-level function - way below the application layer. abc.com and xyz.com are application-level conveniences, understood only by things like DNS servers and web servers. If they both resolve to the same address, that's the address the requests are going to go to. Once the respective HTTP requests get to that one machine (or one of a number of machines if you're using something a little fancy like round-robin DNS), it's up to that machine what sense to make of them. Maybe you could use an HTTP redirect as the response ? Antony.
