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 created my own CA cert, and created a wildcard ssl cert for *

But we use a lot of sub-domains of the form, and I can't seem to create a wild card that will work with this.

* fails on, and creating a wildcard for *.* didn't seem to work.

Is there a way to do this, or do I need to create a wildcard for each subdomain?

share|improve this question

For the record, it doesn't look like it's possible to have . as a wildcard.

We ended up renaming our hosts from to abc-xyz, and then the wildcard worked.

share|improve this answer

You could create ssl certificate for *

share|improve this answer
That's an option, but I'm hoping there is a way to have all subdomains recognized. – chris Jul 2 '13 at 13:13

Its not possible to apply wildcard as * . *, wildcard can secure unlimited sub domain name on the "Same Domain Name" that can secure either * or as Alex said *, in both the term only the value of aster-risk can be changed not the other top or second level domain.

And applying wild card to each sub domain is expensive, you can use SAN SSL if you have limited sub domains, as SAN SSL can secure up to 25 different domains, servers or IPs.

share|improve this answer
The cost isn't really going to be a factor here as the certificates are being self signed with a trusted CA – Matthew Steeples Oct 19 '13 at 11:06

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.