I know that IIS versions 7.5 and earlier do not support wildcard host header bindings.

Have they added it in the latest version (8.5)? I see that it finally supports SNI and wildcard binding (*.mydomain.com) seems like it would be a related feature.


Worth noting that IIS 10.0 does support wildcard host names, see: http://www.iis.net/learn/get-started/whats-new-in-iis-10/wildcard-host-header-support

|improve this answer|||||

I do not think so. When trying to use *.example.com as host header IIS 8 tells me:

enter image description here

So a * is still forbidden as hostheader

|improve this answer|||||
  • Not when done properly with SNI. – Brad Bouchard May 7 '14 at 14:26
  • I tried it on a host which is currently using SNI. No-go to use a wildcard host header. – MichelZ May 7 '14 at 14:27
  • Hmm, Interesting... – Brad Bouchard May 7 '14 at 14:28

Although it wasn't supported, MS did allow multiple certs to be bound to multiple sites on the same IP. The problem was that it usually broke when requests came in.

In IIS 8.5 with the addition of SNI support, you are correct in that it will allow you to do what you are wanting to do now; that is, use a single IP (or many) and bind multiple sites with either a regular SSL or a wildcard.

See here for how to use SNI and wildcards in IIS. (Multiple Certificates using SNI.)

Please note, you will have to tweak some settings, more DNS than IIS, but it will work. See here for how to do a workaround.

|improve this answer|||||
  • This is not what he's asking. He wants to do a wildcard binding. Bind *.domain.com to an IIS Website. Not possible. – MichelZ May 7 '14 at 14:29
  • I hadn't finished editing my answer the first time as I realized that too... thanks for the catch though... – Brad Bouchard May 7 '14 at 14:32
  • The workaround is not very handy. You still need an IP per certificate/wildcard then. I guess what the OP tries to do is having: *.domain1.com as one website, and *.domain2.com as another website, all hosted on the same host. – MichelZ May 7 '14 at 14:35

This is possible, but it requires slightly more work. You will need a dedicated IP address for the site.

  1. Point all domains to the single IP.
  2. Bind the IP to your site without any Host Name.
  3. Write a simple script to inspect the URL and redirect and/or deliver content from the appropriate folder/db etc.
|improve this answer|||||
  • How about site with https (ssl)? – Anh Tú Nov 24 '18 at 2:50
  • That's basically what a reverse proxy does, might as well use nginx. – QAZZY Nov 27 '19 at 19:26

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.