windows - Different domains to different pages in IIS7 -

I have default web site and another web application (let's get it done Application2 < / Em>) inside the default web site in IIS7.

I have 2 registered domain names, say www.example.com and www.example.net .

I would like to configure things when I open www.example.com the default web site , when I open www .example.net I get the default web site / Application2

  www.example.com - & gt; The default Web site www.example.net - & gt; Default Web Site / Application 2  

How can I do this?

First you need to decide whether you want to use name based or IP based hosting. Are there.

Uses an IP-based unique IP to determine which virtual host service will and will use the name-based actual host header.

Scenario # 1 (Shared An IP to do)

You have only one IP server, either private or public, as long as the domain you provide is properly created by your internal or external client Serving From (NAT) Hey.

I recommend that you stop the default website for this tutorial properly.

You will set up a site in II7 and name it accordingly. Go to the right of the manager and look for "binding" under the action menu; Make sure that you have a new site on your left, now select the IP address under "Site Binding", which you will share between sites (name-based hosting). Enter "hostname" domain # 1 "www.example.com", hit OK.

Follow the above procedure with other domains or domains, make sure they have separate hostnames and the same IP.

That's it, you will now be able to start those sites and run them at the same time.

The same principle applies above if using "default site".

Scenario # 2 (Multi IP to share)

If you have left some private or public IPs, then "Default Site" is only a name MS default Made by the form. Or at least as long as you do not exercise, there is only one type of dip that the sites you install will not need to specify "hostname" for each site, because it is basically only in the DNS zone On those sites it will be reacted to any request made on the port of IP 80.

When you have to use multiple IPs to serve websites. Well it all depends.

There are some reasons: Network isolation (security), applications that do not work well under the name-based hosting, SSL certificate binding 443 (pre-II7), and mostly full control over the site. There are definitely more reasons, but I will write a little bit to others.

Have fun.