Potential issues with allowing the user to change the domain name.
In version 138, the user can change the domain name.
I see two problems here:
1) The vast majority of clients are non-technical; they will change the domain, and the site—whether built on WordPress or any other system—will stop working. The client will blame the hosting company, claiming the site worked before. This will generate support tickets and a lot of headaches.
2) What about integration with WHMCS and other billing systems? A client has a hosting plan for *dummy.com*, goes into cPanel, and changes it to *clown.com*. In WHMCS, it will still be listed as *dummy.com*. When the client requests support, they will say their site is *clown.com*, but *clown.com* won't exist in WHMCS. It will take the support technician longer to identify the client.
And these are just the situations that immediately come to mind. There are certainly other potential issues.
My suggestion—which I know cPanel will completely ignore—is to make this feature optional. The server admin should have the option to disallow domain changes.
-
Hey there! We've actually already added a tool for this in WHM >> Feature Manager:
https://docs.cpanel.net/whm/packages/feature-manager/
If you remove the "Primary Domain Rename" option, users won't see this option in their cPanel interface for the main domain.
0
Please sign in to leave a comment.
Comments
1 comment