I second what kazimir82 says in this thread http://forums.cpanel.net/f5/addon-domain-vs-subdomain-vs-username-i-dont-get-203791.html
1) it's strange to force each add-on domain to have their own ftp account, especially in the case of something like example.com and example.org where both are really the same site, this should be optional and should be able to use an existing username.
2) it's not really a good excuse to say "mainly for convenience so say you hired a developer for that one site, you don't need to give him access to the main FTP". Where, then, is the equivalent in the main account that creates an ftp user that's chrooted to the public_html directory?
3) this creates a domain in dns like username.example.com. This exposes the ftp username to the world in dns. This is a terrible idea.
4) I noticed that if you go in and manage the mail accounts, that this username.example.com domain shows up in the list of domains. I really don't want that in there, it's confusing to the user and I can't imagine where I would want to use that.
5) mixing the username in a domain name which is in dns is just wrong on so many levels. They are not the same type of thing and should not be combined and exposed like that.
6) the new ftp usernames that get created are not in fact simply just 'username', they're '[email protected]', this actually is logical. So I really don't understand why you needed to create a domain name username.example.com.
To fix this, can't you just use [email protected] as the unique username instead of username.example.com? And then remove this username.example.com domain, or at least hide it or filter it and don't publish it in dns? I would definitely filter that out of the list of possible email domains. Even if you have to use username.example.com internally, why must this force the creation of a new user and why isn't [email protected] unique enough?
And lastly, as I said in another post, there seems like there should be a way to configure what the public_html directory is called and it should be able to be called by a template that includes $domain so it can be set to the main domain name.
Michael Grant
1) it's strange to force each add-on domain to have their own ftp account, especially in the case of something like example.com and example.org where both are really the same site, this should be optional and should be able to use an existing username.
2) it's not really a good excuse to say "mainly for convenience so say you hired a developer for that one site, you don't need to give him access to the main FTP". Where, then, is the equivalent in the main account that creates an ftp user that's chrooted to the public_html directory?
3) this creates a domain in dns like username.example.com. This exposes the ftp username to the world in dns. This is a terrible idea.
4) I noticed that if you go in and manage the mail accounts, that this username.example.com domain shows up in the list of domains. I really don't want that in there, it's confusing to the user and I can't imagine where I would want to use that.
5) mixing the username in a domain name which is in dns is just wrong on so many levels. They are not the same type of thing and should not be combined and exposed like that.
6) the new ftp usernames that get created are not in fact simply just 'username', they're '[email protected]', this actually is logical. So I really don't understand why you needed to create a domain name username.example.com.
To fix this, can't you just use [email protected] as the unique username instead of username.example.com? And then remove this username.example.com domain, or at least hide it or filter it and don't publish it in dns? I would definitely filter that out of the list of possible email domains. Even if you have to use username.example.com internally, why must this force the creation of a new user and why isn't [email protected] unique enough?
And lastly, as I said in another post, there seems like there should be a way to configure what the public_html directory is called and it should be able to be called by a template that includes $domain so it can be set to the main domain name.
Michael Grant
