1

We have a few websites that we are running on one instance of IIS that need to be mapped for each of their domain names. For example.

Site A has the domain name coolness.com Site B has the domain name 6to8Weeks.com Site C has the domain name PhatTech.com

When I look at the "Web Site Identification" section of the IIS configuration window, I notice that I can specify an IP address and port, but if I click the Advanced button, I can also configure the site based on host header values as well.

How do I configure each site in IIS? Ideally I would like them to all be able to listen to port 80, so I don't have weird URLs, but I'm not sure if I do this using headers, IP addresses, both, or something else.

Improve this question

2 Answers 2

Reset to default
2

type the name into the host header field. leave everything else as it is. job done.

You will need seperate IPs for SSL

Improve this answer
3
  • Can I use a single "SSL" based IP address if I have multiple sites that need SSL, or will I need a new IP for each site I run under SSL? Commented Mar 10, 2011 at 23:20
  • You shouldn't need separate IPs for SSL if you use SSL certificates with Subject Alternate Names (SAN), or wildcard certificates for different subdomains. Commented Mar 10, 2011 at 23:21
  • there are big cost and trust implications with those types of certificate though so while they may be suitable for some situations, generally they are not an option Commented Mar 11, 2011 at 11:07
1

If you have only a single IP for all three sites, you configure it using host headers. All three sites can listen on port 80 on a single IP that way.

Improve this answer
1
  • If I have to expand this server to even more sites, is there any worry about too many sites using the same IP address? Commented Mar 10, 2011 at 23:19

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.