Overview

If you are on a reseller package this does not apply to you. This thread only applies to users shared hosting packages with multi-domain support.


Some people would like to host two (or more) domains in the same web space for their existing package. This is called an "addon domain." Some people prefer addon domains, and some prefer a separate hosting account, it is really a matter of personal preference. I prefer a separate hosting account to keep myself better organized.

Addon domains allow you to share web space with several websites, and allows you to use one, consolidated control panel for all domains. They allow you to use one FTP user account for all domains, or, you can have a unique FTP user for each site (recommended)

If you are on a qualified plan, the first step for using an addon domain is to point the DNS for the desired addon domain to the same DNS your main site uses. It will be similar to:

nsx.glowhost.net
nsy.glowhost.net

 

Please, note, that the NS above are given as an example, you need to use the NS provided in your Welcome letter for your main domain.


Check your login letter for your "master" or "root" domain to be sure what these are, or you can do a WHOIS lookup on the domain to find out what nameservers you are using.

Then you may need to wait 24-48 hours for the domain to resolve, but usually it can be done in only a few minutes.

After you have pointed your domain nameservers, and given enough time for them to resolve:
-----------------------------------------

Login to your control panel and click the icon for "Addon Domains."

1. The first box is for your new domain name: example: mynewdomain.com
2. The second box is for the subfolder or subdirectory that you want to act as public_html for the new site.
cPanel calls this: (Username/directory/subdomain Name) example: mynewdomain
3. The third box is for the ftp password for this account. example: HJDII59UGF

In the above example, you have just made an addon domain for mynewdomain.com. You have also created a unique ftp user account called mynewdomain@master-domain.com with an FTP password of HJDII59UGF

Your addon domain has been created!


Addon Domain FTP Configuration Information (basic)
-----------------------------------------------

You can configure your FTP program using the example scheme above. Your hostname would be master-domain.com - Introduction for all accounts in the above example.

 

In the remote directory option for each addon domain, you need not type anything into this field.


This is opposite of how your master domain remote directory field works. With the master domain, you should specify a directory. Normally, public_html (or www for short)

To recap, your config would look like this for each addon domain:

 

 hostname: master-domain.com - Introduction
 Remote directory: {leave this field blank for addon domain ftp users}
 Username: mynewdomain@master-domain.com
 Password: HJDII59UGF


This user cannot navigate any higher than the mynewdomain directory. In other words, this addon domain ftp user user cannot gain access to the main site's public_html folder.


One FTP for all accounts (advanced)
--------------------------------------

Alternatively, you can ftp into the master domain's FTP account and descend into each addon domain site by opening the folder you selected above to act as pubic_html. In this case, you would use:

hostname: master-domain.com - Introduction
Remote directory: /public_html/mynewsite
Username: cPanel-username
Password: cPanel-Password


Your master domain's ftp account differs in that there is not a @master-domain.com extension on the username. The master account ftp username is the same username that you use for your cPanel username. I marked this on as advanced as it is easier to accidentally trash the wrong site unless you are extremely comfortable with FTP. My suggestion is to use unique FTP usernames for each addon domain if you are just starting out.

 

Related articles

Related articles appear here based on the labels you select. Click to edit the macro and add or change labels.

Related issues