Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have server 2008 installed on one of my servers. I have two domain names, which i want to configure for two different website in IIS7. I already configured one site for one domain name , which is using port 80. How do i configure multiple websites, which can be accessed by different hostnames

thanks

share|improve this question
    
Same thing as in this question (even though it specifically says internal): serverfault.com/questions/68020/… –  squillman Oct 16 '09 at 20:10

1 Answer 1

You need to configure each website to respond to the correct host header. This will enable you to serve both sites on the same port on the same server. For example www.domain1.com and www.domain2.com. If you only have one domain, you can specify a different host name (e.g. site1.domain.com and site2.domain.com).

In IIS7 you set the host name in the site bindings dialog box.

Step by step instructions:

  1. Open Control Panel

  2. Open Administrative Tools

  3. Launch Internet Information Services (IIS) Manager (Note: Do not open the 6.0 Manager.)

  4. In the connections pane, twirl open the tree until you see the website you've created previously

  5. Select the site

  6. In the Actions pane, click the Bindings link

  7. Select the binding you want to edit

  8. Click on the Edit button

  9. Add the appropriate host name (e.g. site.domain.com; do not include http:// )

  10. Click on OK, then Close

share|improve this answer
    
You need to configure each website to respond to the correct host header. This will enable you to serve both sites on the same port on the same server.-- How do i do this? Apologies for my ignorance, im not really a server guy :( –  user23187 Oct 16 '09 at 20:32
    
hi, After configuring the binding settings, when i try to browse the site it returns 404 not found? do i have to do anything else? –  user23187 Oct 19 '09 at 3:25
    
No, a 404 is actually somewhat of a good sign. It means the site is responding to requests. It's likely that you don't have a file in the web root that IIS can serve. –  kevintechie Oct 19 '09 at 21:25

Your Answer

 
discard

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.