usernames as sub domain of a user's domain

[mgrant]

When I go to add a domain to a cpanel account, it wants to create a new username for the ftp account for that domain. It takes that username and makes a sub-domain out of it like:

username.example.com

so this became the ftp username for this new domain. What strikes me as odd though is that this also became a real sub-domain of example.com. Why did it need to do that? Is there some tweak to hide these extra domains or some setting so that it does not create a sub domain?

At first I just ignored these extra sub-domains but the problem is that they start to get in the way and become confusing. When the user goes to create a mail account or a forwarding address, they are presented with username.example.com in the list of domains. It becomes clutter.

It makes me wonder if the cpanel/whm is actually configured correctly.

Michael Grant

 

[mgrant]

Oops, I see I must have pressed the submit button twice on this.

No takers on this? Can anyone explain to me the logic behind what's going on? Why is it creating these sub-domains?

Michael Grant

 

[Infopro]

When I go to add a domain to a cpanel account, it wants to create a new username for the ftp account for that domain.

You mean, addon domain here I assume.
Addon domains need a user to login with, [email protected] is that users login.

Why did it need to do that? Is there some tweak to hide these extra domains or some setting so that it does not create a sub domain?

If I understand you correctly, that's how the system works. If you wanted to change that, you'd want to change this setting:
WHM » Server Configuration » Tweak Settings, Domains tab.

public_html subdomains only [?]
Prevent users from creating subdomains outside of their public_html directory.

With that setting changed to allow subdomains outside of public_html, when you go to create the addon domain, look closely at the Document root section of the form. When you type in the new addon domain, the doc root is auto filled. You can edit that path before you actually add the addon domain, removing the public_html/ part.

When the user goes to create a mail account or a forwarding address, they are presented with username.example.com in the list of domains. It becomes clutter.

The more domains you add, the more "clutter" you can expect. The above change may be helpful, but the domains on the account will still be there. Giving these domains their own cPanel account might be more useful and less cluttered.

It makes me wonder if the cpanel/whm is actually configured correctly.

Seems fine to me.
Addon Domains - cPanel Documentation

HTH!