I have one SSL certificate that is valid for multiple domains. It's not a wildcard cert and it is not for sub-domains. I have the site1 setup properly on IIS7 with the SSL cert bound properly. This binding for site1 maps * IPs with no host header to port 443.
I need to setup site2, a totally different domain, on a new site node, but pointing to the same certificate. When I do this, since I cannot enter the host header, when I browse to site2 and it responds with site1 on SSL. This makes sense because neither binding has a host header specified.
This machine only has 1 IP address, do I need another IP to bind site2 to the same certificate? Should the binding specify the IP address rather than "(All Unassigned)"? Will my solution involve specifying the host header for these sites somehow?
Best Answer
You have 2 options.
Use another IP as you've mentioned.
You will need to manually edit the IIS 7 config from the command line. I've outlined the steps here: link
Doing this will override the default settings of IIS 7 to allow the same cert to be used on different sites with the same IP. It's a common step everyone had to take in the IIS 6-7 days.