Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

How addon domains are handled in cPanel question

Discussion in 'General Discussion' started by HHaaland, Jun 9, 2017.

  1. HHaaland

    HHaaland Registered

    Joined:
    Jun 9, 2017
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    1
    Location:
    Norway
    cPanel Access Level:
    Root Administrator
    Thanks for a great product in general! I've been away from cPanel for many years, and returned to the product when I change my VPS in May.

    I've been trying Atomia and before that Plesk for webspaces before I've got my own servers and VPS.
    And I have to say, I'm starting to regret not choosing Plesk for my VPS.

    Why have cPanel choosen to use subdomain with Addon Domains?
    I havn't tried ANY other control panels that use this solution. It makes problem for the SEO (I found a work around for this I think), and it's also making a Zone File that just getting bigger and bigger and bigger and bigger.

    As I understand, there is no plans for changing this?
    But I would love to know the reason for why this solution is choosen.

    And since you not going to change it, even with so many feedbacks about it. Why not change the controlpanel to have "account users", with it's own control panel for each domain? (if you understand what I mean)

    Hope to hear from Cpanel about this.

    And for other users, why not answer the poll?
     
  2. Infopro

    Infopro cPanel Sr. Product Evangelist
    Staff Member

    Joined:
    May 20, 2003
    Messages:
    15,766
    Likes Received:
    313
    Trophy Points:
    433
    Location:
    Pennsylvania
    cPanel Access Level:
    Root Administrator
    Twitter:
    Poll removed, no need for one on this.

    If I understand your issue properly, when creating an addon domain, edit the Document Root field from this:
    public_html/example.com
    To this:
    example.com

    That should place the addon domain outside public_html.
     
Loading...

Share This Page