Hey there! Everything can now be done under the Domains section. If you create a domain with the same document root, it's an Alias. If you create a domain with a different document root, it's an addon.
We're doing this as we slowly try and get away from the concept of a "main domain" for a cPanel account.
We're doing this as we slowly try and get away from the concept of a "main domain" for a cPanel account.
I would encourage cPanel to drop the whole "domain alias" thing and just make everything an addon domain.
Domain Aliases get added as a ServerAlias to the parent domain's VirtualHost... meaning that every time an alias is added the certificate has to be regenerated to include ALL of the aliases associated with that ServerAlias (and what do you do with the aliases that no longer resolve to the server?) on the SANs
An Addon domain - with the same DocumentRoot - makes a lot more sense to me. An Addon domain gets it's own VirtualHost entry. No need to regenerate the entire certificate each time an alias is added. Domain stops resolving to the server? That certificate just simply does not get renewed.
We stopped the practice of doing Domain Aliases years ago in favor of this Addon Domain structure. It's a lot cleaner and a lot simplier when it comes to secure certificate issuance.
Domain Aliases get added as a ServerAlias to the parent domain's VirtualHost... meaning that every time an alias is added the certificate has to be regenerated to include ALL of the aliases associated with that ServerAlias (and what do you do with the aliases that no longer resolve to the server?) on the SANs
An Addon domain - with the same DocumentRoot - makes a lot more sense to me. An Addon domain gets it's own VirtualHost entry. No need to regenerate the entire certificate each time an alias is added. Domain stops resolving to the server? That certificate just simply does not get renewed.
We stopped the practice of doing Domain Aliases years ago in favor of this Addon Domain structure. It's a lot cleaner and a lot simplier when it comes to secure certificate issuance.
I agree with the hassle part, but not with getting rid of aliases.
Many providers (we do, too) charge/restrict based on addon domain count, but we allow unlimited alias, because we don't want to charge for a redirect or for e-mail accounts.
That is a big feature for us to have mailing on dedicated email accounts for alias domains. Our previous hosting panel could not do that.
