Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have an existing web server that has been running multiple, related, domains all under 1 wildcard SSL certificate using host headers. *:443 *:443

I have now introduced a completely new domain onto the same server,, which requires its own SSL certificate. I know that I cannot associate 2 SSLs with the same IP address so I have specified individual addresses in the bindings...

Both the original domains work perfectly and the new domain works under http. HOWEVER, I cannot navigate to as it tries to load the * certificate. If I browse to the browser shows the correct certificate. I have also confirmed on that correctly resolves to

I'm not a network / server guru - can anyone help with this?

share|improve this question

Typical. This has now just magically corrected itself! I suspect it was an issue with propagating DNS records.

share|improve this answer

Your Answer


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.