Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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

our server url schema is setup like this:

customer-domain.extension.clients.example.com

For example:

customer-domain.net.clients.example.com

So the clients.example.com never really changes but customer-domain and extension do.

What would be the most reliable and cheap way to set up SSL certificates for this server?

Thanks, Slav

share|improve this question
up vote 2 down vote accepted

The RFC states that wildcards are only good for the next level down. So in your above examples you would need to get a wild card for each extension:

*.extension.clients.example.com

Personally, I would drop the extension part of your scheme and have a wildcard for

*.clients.example.com

Now, some browsers support multiple levels for wildcard certs, but this is not universal and against the RFC anyway.

share|improve this answer

Your Answer

 
discard

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.