>I took a look at that page. At first view, this seems to target about URL rewriting in regards to how we negotiate with a hit from a specific Web site. In my case, I have something like this:
>
>http://www.mydomain1.com
>http://www.mydomain2.com
>http://www.mydomain3.com
>http://www.mydomain4.com
>
>In IIS, I have:
>
>IIS site for mydomain1
>IIS site for mydomain2
>IIS site for mydomain3
>IIS site for mydomain4
>
>The first issue would be to have something like this in IIS:
>
>IIS site for all domains
>
>So, I would need to find a way to have IIS setup so it would know that it should process all those domains into that "IIS site for all domains". Is this possible?
>
>The way I do it right now, is that my ASP.NET application reads the URL and knows to which client it belongs. During the initialization of the hit, once the client has been found, I can initialize the client parameters. So, I guess the issue mostly relies on how to have a IIS setup which would know how to process hits on all those domains into the "IIS site for all domains". AFAIK, an IIS site points to one IP address. Or, is there some kind of other ways to do it?

Sorry, just about to dash off and haven't read this carefully but

(a) you can do a rewrite to a completely different domain name.
(b) a domain name can only point to one IP address but one IIS web site can handle multiple IP addresses (thus multiple domain names) - open the property page for the web site, 'Web Site' tab, Advanced button and add additional IPs from there.....