Addon Domains / Alias Domains

Ned

Hey All,

Looking to see if the addon domains feature has any planned change or upgrades.

Right now one of the major downsides of how they are handled compared to other products is that they don't give the end-user ease of access in setting one up or installing a WordPress application on it.

Having the new docroot pre-filled based on the domain name would be good - so if they enter domain2.com the advanced tab will pre-fill "public_html/domain2.com" as the docroot

Having the ability to install apps onto addon domains would also be great

Hope to get your input on the feature too 🙂

necrom

I personally like the (mostly) 1:1 relationship between containers and domains which seems to be designed by default; its a helpful reminder to avoid the pitfalls of other panels where many domains end up sharing the same container/resources and it becomes difficult to scale or debug.

For my needs we will (mostly) only be allowing more than one domain for aliasing or small sub-domains, otherwise if the customers needs two fully fledged applications (say example.com being Wordpress and shop.example.com being Magento) then we'd expect them to have two package subcriptions. We'd definitely want a Wordpress instance on example1.com and another Wordpress instance on example2.com be two containers/package subs.

Granted it's a difficult one to explain to end users and I'm not sure if the current language o UI is the best way of doing it.

Ned

necrom

I do like the container approach and that the addon domains would live in the same container, The way I see it however is that if a client chooses to use one "Container" or website and add an addon domain to it there's no real reason that the app section of the website/container couldn't also facilitate the addon domain.

Right now you have the ability to install multiple apps to the subfolder of the main domain, If there were going to be any quality-of-life updates made to addon domains having them featured there too would be a nice touch.

I've come to terms with the fact that to make enhance work we will have to charge per domain, But it makes bringing across any existing cPanel/DA customers a bit more difficult when they have a large number of additional domains that are capped by the same LVE/Container limits on their existing plans.

Adam

Hi Ned,

Thanks for the suggestion. We do plan to implement something very similar to what you suggested to make installing WordPress easier on addon/subdomains. This will hopefully be in a forthcoming update.

Good suggestion on the UI auto-complete for the document root, I'm sure we can do something around that. We may need to add a toggle to differentiate between aliases and domains which deliberately serve different content.

Kind regards,

Adam.

prasad0889

Just wrote the same thing today, to find out that his has been already mentioned. This is definitely needed.

PradeepC

Hello Team, Any update on this?
I am looking at a feature where, the document root for addon domains would be inside of public_html only and not outside it. From what I know, if the website resides outside of public_html then it will be counted as 1 website. So if a client adds 50 such domains outside public_html, we will be billed for 50 websites for the client, while we do not charge him for 50 websites.

Correct me if I am wrong, even if a user has set the package to 1 website, and 50 addon domains/websites, if the user selects a directory outside public_html for those 50 addon domains/websites we will be billed for those websites? But if the websites sit under public_html then we will be billed for 1 website, right?