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 wonder if someone can help me - I'm a complete newbie when it comes to administering servers so apologies if I'm missing something obvious...

We've decided on a naming convention which uses Elements from the periodic table (with VM Hosts as molecules)

While this is okay for the time being, I'm not relishing the prospect of typing "Unununium" or "Ununnulium" when we've got that many servers. So... i've added some DNS entries for the chemical symbols (He->Helium, Li->Lithium, etc.)

When i attempt to RDP to the servers using the DNS alias, I get a certificate warning as (obviously) the name I'm connecting to doesn't match with the server in question.

Whilst this is only an annoyance for RDP I'm assuming it may have implications if i use the shortened names for other purposes.

So, my question is - Is it possible to have the server I'm connecting to use a certificate which covers both? or have 2 certs side-by-side and auto-select the correct one?

As I said, I'm new to this so am a little unclear as to what options are available to me and would appreciate it if someone would point me in the right direction for some useful documentation / guides.

Many thanks in advance for any help you can provide

I should've mentioned, the servers in question are running Windows Server 2008 Enterprise and the clients will all be either the same or Windows 7

share|improve this question
up vote 3 down vote accepted

You can generate certs that are good for multiple DNS names using the Subject Alternative Name property. It's not as easy as a single wildcard cert for all of your machines, but it's a lot more secure. Here's an article from DigiCert about Subject Alternative Names and how they're used.

Basically, you'll generate a cert for each server that contains SAN entries for each dns name you're likely to access it with.

share|improve this answer
Fantastic - does what I need and is secure. thanks – Basic Feb 7 '10 at 15:18

A wildcard SSL cert would do the trick, I believe.

share|improve this answer
Thanks, that's really useful to know and I'm sure it's going to handy in future. I would +1 but I don't have the rep on SF yet. – Basic Feb 7 '10 at 15:19

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.