addon domain and root directory question

Discussion in 'Site & Server Administration' started by Swerd, Feb 4, 2009.

  1. #1
    Hey,

    I recently upgraded servers and cpanel.

    In my old cpanel the addon domains root folder is public_html/domainname

    In the new cpanel it sets this automatically to public_html/domainname.com

    Quick question. why does it have the .com on the end now?

    Is it simply because some people had the same domain but with a .net, .org etc and this made it easier.

    if this is the case, does the username need to be domainname.com domainname.org etc for each one?

    Will it make any difference at all whether I use a .com on the end of the folder name or not?
    eg would one work any faster, is one a more common standard?
     
    Swerd, Feb 4, 2009 IP
  2. Colbyt

    Colbyt Notable Member

    Messages:
    3,224
    Likes Received:
    185
    Best Answers:
    0
    Trophy Points:
    210
    #2
    I do not know why it is that way but I would not change it. I personally like the feature as it divides the directorys from the addons in a very clear manner. For testing purposes browsers seem to have no problem reaching mainsite.com/addononsite.com though you should not do that except in a have to case where the dns has not propagated.

    When adding on a domain if you tab to the next window the username is populated auotmatically by cPanel and I seem to recall it is without the .ext.


    edit: Thought of this after I left. It may also affect your stats. cPanel 11 provides for nicer stats than I have ever encountered with the older versions for addon domains.
     
    Colbyt, Feb 5, 2009 IP
  3. sparek

    sparek Peon

    Messages:
    68
    Likes Received:
    6
    Best Answers:
    0
    Trophy Points:
    0
    #3
    It doesn't really matter. The path is just setting a document root to your addon domain.

    You could have an addon domain that is example.com and have it point to the directory /home/user/public_html/asdfjkl and that will still work. Not quite as clear to the human eye as to what the purpose of the asdfjkl directory is, but it would still work.

    There's no real correlation between the addon domain and the directory hosting that addon domain.
     
    sparek, Feb 5, 2009 IP
  4. geek4ever

    geek4ever Peon

    Messages:
    36
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #4
    I think it's safer to leave the addon directory name as specified by your cpanel. This way, there'll be boldness just in case something goes wrong and you'll need to contact support.
     
    geek4ever, Feb 5, 2009 IP
  5. Swerd

    Swerd Active Member

    Messages:
    1,657
    Likes Received:
    25
    Best Answers:
    0
    Trophy Points:
    90
    #5
    thanks for the answers, When they upgraded my server they copied all of my files over to public_html/domain/

    However when the add domains where added (by them) they defaulted to public_html/domain.com

    So all of my site root folders dont have a .com at the end.. This mismatch resulted in just under 3 days of down time and a lot of money!!

    For now I have changed the root folders and removed the .com part. I would personally like to have it as the default setting (with .com) just in case I need to speak to support.

    I have tried uploading all of my sites to a .com root folder but this would probably take about a week to do. Hostgator should be able to do this for me right?

    Also, anybody here know if hostgator would be nice enough (and business minded enough) to re-inburse my financial loss in the form of discounted hosting?

    Thanks again for the replies,

    Swerd
     
    Swerd, Feb 5, 2009 IP
  6. gilmapaiyan

    gilmapaiyan Peon

    Messages:
    32
    Likes Received:
    1
    Best Answers:
    0
    Trophy Points:
    0
    #6
    you could manually change to anywhere.. even a dir outside your public_html.. i normally host addon domains in a root folder called domains.. so that it is nt available from the root domain
     
    gilmapaiyan, Feb 5, 2009 IP