Addon Domain in cPanel: 7 Easy Steps to Add or Remove One

An addon domain lets you host a separate website under another domain name on the same cPanel account. It normally has its own document root—the folder that contains that website’s public files.

For example, you might host your main business website and a second project in one account. Each needs the correct domain configuration, website files, DNS records and HTTPS setup. Adding the name in cPanel is only one part of getting it online.

This guide explains the current Domains interface, what to check before removing a domain, and how to avoid mixing up the two websites.

1. Check your addon domain allowance

First, confirm that your hosting plan allows another website. Domain limits, storage and available features vary by package. If cPanel does not offer a separate document root, ask your provider whether addon domains are enabled.

You must also own or be authorised to use the domain. Creating a hosting entry does not register it, renew it or transfer it from another registrar. Keep its registration active separately.

For an existing website, take a backup before changing its domain or folder settings. Record the current DNS, document root, databases and email arrangements so you know which services must stay working.

2. Create an addon domain in cPanel

1. Sign in to cPanel and open Domains.
2. Select Create a New Domain.
3. If a domain-type choice appears, choose the option for an existing registered domain.
4. Enter the domain, such as example.net, without a protocol, page path or unnecessary www prefix.
5. For a separate website, clear Share document root with the main domain.
6. Review the suggested document root and any associated subdomain fields.
7. Select Submit, then confirm that the domain appears in the list.

The exact fields depend on your version and hosting configuration. See cPanel’s Create a New Domain instructions. Older accounts may still show a dedicated Addon Domains screen.

3. Choose the right document root

Give an independent website its own folder. A recognisable folder name makes uploads, backups and future maintenance easier. Use the path accepted by your hosting account rather than assuming every server permits the same folder layout.

Goal	What to check
A separate website	Use a separate document root and upload that site’s files there.
Another name for the same website	Review whether a shared-root alias is appropriate, including canonical URLs.
Send visitors to a different URL	Use a redirect rather than expecting a folder setting to redirect the browser.

If a folder already contains files, inspect them before using it. Do not dismiss a warning about an existing folder or subdomain until you understand why it appeared. Accidentally pointing two sites at the same application can create confusing content and configuration problems.

Changing the document root later changes where the server looks; it does not move your website files. Review the Manage the Domain documentation before changing an existing setup.

4. Connect the addon domain’s DNS

Make the required changes at the authoritative DNS provider. Your domain’s registrar, DNS provider and website host may be different companies.

A website move may need A or AAAA records updated, while a DNS-provider migration needs the complete zone copied and checked. Keep existing mail records unless email is moving too. See How to Change DNS Zones for worked examples and verification commands.

Allow for cached DNS answers when testing. A record saved in a dashboard is not proof that every visitor is already reaching the new server. Compare the authoritative answer with the result from your usual resolver.

5. Upload files and test the website

Open the domain’s document root in File Manager or use a file-transfer method supported by your hosting plan. Upload the intended website there, or install your application into that folder. Database-backed sites also need their database and configuration set up.

• Check the homepage and internal pages. Confirm that you see the correct project, not the main website.
• Test HTTPS. Wait for a valid certificate to be available before forcing secure redirects.
• Review application URLs. A copied WordPress installation may still contain the previous site address.
• Test email separately. Hosting a second website does not automatically recreate existing mailboxes.
• Keep credentials securely. If you create a separate file-transfer account, store its password in a password manager.

An addon domain is still part of the same hosting account. For projects requiring stronger administrative separation, discuss separate hosting accounts with your provider.

6. Remove an addon domain without losing track of its data

Before removal, back up the account and check whether the domain still receives visitors, email or automated requests. Arrange any migration or redirects first. Removing the hosting entry does not cancel domain registration.

1. Open cPanel → Domains.
2. Find the exact domain and select Manage.
3. Review its document root and dependent services.
4. Select Remove Domain.
5. Read the confirmation and proceed only when you intend to remove that hosting entry.

cPanel documents that removal deletes the domain’s web-server and DNS entries while retaining its directory and contents. External DNS is managed separately. Associated email accounts disappear from the Email Accounts interface, although their mail folders remain on the server. Back up needed messages and confirm the migration before removal.

Do not treat removal as complete data cleanup. Review leftover files, databases, users and scheduled tasks separately, and check that another website does not use them before deleting anything.

7. Troubleshoot common addon domain problems

The domain cannot be added

Check the plan limit, spelling and whether the domain is already configured on the server. Ask support to inspect ownership or server-side validation errors. Repeated submissions will not resolve a conflicting domain entry.

The domain shows the main website

Check whether the document root was shared accidentally. Then inspect the actual DNS destination, server configuration, application URLs and any cached redirects. A wrong page is not always a DNS problem.

The website returns a 403 or 404 response

Confirm that files are in the selected document root, the expected index file exists, and permissions match your host’s requirements. Review application routing and logs rather than broadly relaxing file permissions.

HTTPS shows a certificate warning

Check that the certificate covers the hostname and that DNS reaches the intended server. Ask support to review certificate issuance or installation. Do not bypass the warning as a permanent fix.

Frequently asked questions

Is an addon domain the same as a subdomain?

No. An addon domain normally uses a separate registered name, such as example.net. A subdomain is a name under an existing domain, such as shop.example.com.

Does adding a domain create a website automatically?

No. The hosting entry identifies where the website belongs. You still need working DNS, content or an application, and an appropriate HTTPS setup.

Can I remove the main domain this way?

No. cPanel treats the main domain differently. Contact your provider if you need to change the account’s primary domain.

Will removing the domain delete my database?

Do not assume removal manages the database lifecycle. Keep backups and review databases independently, especially if more than one application uses them.

Need help with your domain?

Send DigitalBerg support the domain, intended document root and any error message. Explain whether you are adding a new website, moving an existing one or removing old hosting. Never include account passwords.

Reviewed: 29 October 2026. Based on the official cPanel documentation linked above. Example domain names are illustrative.