cPanel & WHM Version 92 has been released, and brings a slew of great updates. Take a look at what is included, and then upgrade today!

Remove requirement for a subdomain when creating an addon domain

Mike shared this idea 3 years ago
Open Discussion

As a cPanel user, a server administrator, and a web hosting provider, I would like cPanel to allow the addition of addon domains, and move the creation a related subdomain to an option, to improve usability in any domain-related interface.

These unnecessary and unused subdomains can litter the cPanel interface. I'm sure there's a reason behind their use but I'm also thinking the reason is probably historical and no longer relevant in 2017, perhaps I'm wrong though.

Comments (8)

photo
1

I totally agree, most of my clients have come from other panels and find it very confusing to be confronted with a multiplied amount of domains when creating accounts for mail, ftp and also when checking AutoSSL-status. Many clients have 5-10 domains, so when they create new accounts for mail, ftp etc. the list of sub-domains gets really really cluttered.


When creating new mail- or ftp-accounts, the user should really only see the relevant assets such as main/primary-domain, addon-domains and those sub-domains that they have created actively.


Any subdomain related to his primary-domain should be removed or at least they should be made invisible for better UX.

photo
1

Would like to leave a bit more information for any other users who see this and are wondering what is going on.


Say your cPanel account is for example.com. You want example2.com to redirect to example.com, so you add it to cPanel as an addon domain.


cPanel creates the subdomain example2.example.com. And in addition, as mentioned by Sascha, you will see the following entries added to the AutoSSL system.

http://www.example2.example.com

cpanel.example2.example.com

whm.example2.example.com

webdisk.example2.example.com

cpanel.example2.com

whm.example2.com

webdisck.example2.com


That is a lot of extra entries that you didn't want. The good news is the team at cPanel is aware of this and already on-board, it will just take a lot of refactoring on their end.

photo
3

Actually I wish cPanel to completely renew the way our clients have to deal with domains:

1. Replace "Addon Domains" with "Domains" (terminology & location)2. Stop creating Sub-Domains for each Addon-Domain - this is crazy stupid from clients perspective: They only want to add a new domain to their account for websites, mail etc. Wherever they need to setup a new account (mail or ftp) or website (via Softaculous) for this domain, they are confronted with a list of 1. primary-domain 2. addon-domain 3. subdomain-or-addon-domain.primary-domain, so they raise support-tickets to ask "What is this under 3.???" and its really really getting worse as soon as your clients add a few more "addon" domains. Makes it very hard to onboard clients who come from other hosting-panels!

Why don't you just hide those additional sub-domains? They are not usefull from clients view at all, but rather disturbing. I know that your system "needs" them, so keep them alive for the system, but hide them from our clients please

photo
3

Completely agree -- was just dealing with this yesterday and was not able to accomplish what I wanted without a bunch of needless additional subdomains.

photo
4

This can get even worse if you have 2-3 subdomains with different .tld.

adding domain.com, domain.org. domain.example, domain.org.example will get a conflict of folders when parked/addon multiple of these..

photo
2

This really causes a huge mess. Obviously separate domains are totally unrelated, why would subdomains be created on the first domain used when setting up cPanel. If anyone wanted that, they would create the subdomains themselves. When you have 10 or more domains it's hard to navigate through huge lists of nonsense subdomains while trying to find the couple that I created. Please address this. Thank you.

photo
4

This is creating a lot of mess and when you are using Let's Encrypt we are asking for non used SSL for non used subdomains. Also is is rly easy to exceed LE limits.

photo
1

I have a domain, suppose it's name example.com. I have 3 other clients and their domains are also hosted in my server. By the way, mine is a shared server. Now, let's assume the other 3 domains names are dot.com, url.com and http.com respectively. Now, after adding their domains as 'add-on domains', 3 other subdomains have been added automatically, named, dot.example.com, url.example.com and http.example.com and this is confusing. There should be only dot.com, url.com and http.com and should not be any subdomain because if I want to create some subdomains for my own use those will be like developer.example.com, store.example.com and if my clients want to do the same, create some subdomains for their own, it will be a mess and very quickly my subdomain quota will be exausted. So, please rectify or redesign it so that domains can be added as 'domains' only and no subdomains would be created automatically. You can mark the 'Primary' domain as 'Primary'. I know you can do it. Maybe you are afraid of your huge customerbase who might have to reconfigure their websites which may raise a negative impact. But, history has the proof that every positive action got some negative reactions but they have been implemented for greater good. Please do this and you will not regret it and cPanel will get much more acceptance without raising any eye brow of the migrating customers from other platforms who have not faced this type of awkward mess.

Regards.

photo
3

Really, "awkward mess" is an appropriate term. This MUST be changed. It is confusing and, from the user's point of view, simply wrong. Users want to have domains and subdomains. Not subdomains that appear in both lists and also confuse them regarding their package's limit.

If the implementation is too complicated, can't you at least hide this and let it happen in the background?

photo