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'm trying to figure out a structure for a hosted application that i'm working on. I've got a domain lets call it (a sub-domain of course) that is setup to redirect to my IIS 6 web server.

I would like to set up one website in IIS for each client that will use this application. And have the URL schema be like this: --> would point to ClientA website in IIS --> would point to ClientB website in IIS

Do you guys have any pointers or best practices for my scenario?

share|improve this question
Are these just separate websites or are you trying to do something special, like pull up the same website via different urls? – Cypher Oct 23 '10 at 4:22
Everything old is new again... that's how they used to do virtual hosts before host headers were universally adopted... – Bandrami Dec 23 '13 at 8:34

Use a redirector. gets redireted to

Pretty much every reverse proxy should do. It can also rewrite the HTML in the pages when needed.

Pretty much the only solution I can see.

share|improve this answer

Vdirs need to be under the same site unless you front the site with a load balancer or proxy of some sort.

Can you use If so, then you can use the unique domain names (cnames) for each site.

share|improve this answer
Hi Scott, thanks for the reply. No i'm afraid that it wouldn't be acceptible for us to use the approach. – user28502 Dec 10 '09 at 11:34
Your only option then is to front the sites with a load balancer. If you're starting fresh, I would recommend IIS 7 + ARR. You can do layer 7 routing that way. – Scott Forsyth - MVP Dec 10 '09 at 12:18

Your Answer


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