What about CSR code SAN fields? Print

What about CSR code SAN fields?

When generating a Certificate Signing Request (CSR) for a Multi-Domain SSL, you may notice that some advanced CSR generators include a section for SAN (Subject Alternative Name) fields.

At Nixzoehost, we aim to make the activation process as simple as possible. Here is the lowdown on how to handle these fields during your setup.

1. Are SAN fields in the CSR mandatory?

No. You are not obligated to fill in any SAN fields when generating your CSR code.

For the vast majority of our users, the best practice is to:

• Use your Primary Domain as the Common Name in the CSR.

• Leave the SAN fields blank in your server's CSR generator.

2. Where do I add my other domains?

If you don't put the domains in the CSR, where do they go? When you paste your CSR into the Nixzoehost Activation Wizard, our system will automatically detect that you are using a Multi-Domain SSL. A dedicated set of text fields will appear on our website, allowing you to manually type in all your additional domains and subdomains.

Why this is better: It allows you to easily edit, add, or swap domains during the activation or reissue process without having to touch your server's command line or cPanel CSR tool again.

3. What if I did include SANs in my CSR?

If your web server or an external tool (like OpenSSL) automatically included SAN fields in your CSR:

• Our system will read them: The Nixzoehost dashboard will typically "pre-fill" the domain fields based on what it finds in your code.

• You can still edit them: Even if they are in the CSR, you can usually add more domains or correct typos in our dashboard before you hit the final "Submit" button.

4. One Crucial Rule: The Main Common Name

While SAN domains are flexible, the Common Name (the primary domain) you used to create the CSR is much more rigid.

• It cannot be changed during activation: If your CSR was made for example.com, you cannot decide to make another-site.net the primary domain during the wizard.

• The Solution: If you realize the primary domain is wrong, you must generate a brand new CSR with the correct Common Name before proceeding.

Technical Summary for 2026