Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am configuring Application Request Routing on IIS 7.0. More information could be found here,

My development/deployment environment is, IIS 7.0 + Windows Server 2008. I have several web sites, each of them has stable and beta version, for example, I have beta version order system and stable version order system, the same as purchase system. I deployed the 4 systems on 4 different physical machines (machine name labvm1, labvm2, labvm3 and labvm4).

My requirement is, I want to have a common URL schema to access the different systems, like,

But since the 4 systems are deployed on 4 different physical machines with different machine/DNS name, how could I setup URL rewrite rule to map the same domain ( with different suffix to different physical online systems? BTW: I want end user in browser to see, other than expose internal machine name like labvm1.

thanks in advance, George

share|improve this question

The alternative is to create the redirects on the server hosting Create dummy websites for each of the four sites with a dummy default page as you 'll need this when going through the website creation wizard. Then, going back into each website change the url path to a redirect URL of the actual server hosting the website.

But, before hand you will need to setup subdomains for each of the websites i.e, Point these to each of the servers in DNS. So when the end user enters the redirect will take them to


share|improve this answer
Creating dummy sites will make end user to see internal server name from browser address bar because of redirection is used. – George2 Jul 15 '09 at 10:59
I have a related question here, appreciated if you could take a look.… – George2 Jul 21 '09 at 12:07

Hmmm, my instinctive response to this would be to use ISA Server or some other form of reverse proxy. I think even SQUID would do it (and SQUID is free). You just configure the reverse proxy rules so the requests get routed to the appropriate internal server. As far as the end use is concerned they just see your proxy server and they wouldn't be aware of all the stuff behind it.

If you want to stick with MS software then I'm 99% sure ISA 2006 (and probably earlier versions) using a web server publishing rule, which is in effect a reverse proxy.


George2 asked why I wasn't recommending ARR: I'm sure ARR would work. However, while I've read the white papers, I've never used it in anger. If I want a reverse proxy my instinct tells me to get a reverse proxy rather than an IIS addon that does reverse proxying. If you might need the other tricks that ARR can do then obviuously choose ARR.

share|improve this answer
Why ARR is not recommended? :-) – George2 Jul 15 '09 at 10:58
I have a related question here, appreciated if you could take a look.… – George2 Jul 21 '09 at 12:08

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.