If you manage multiple websites or want to organize different sections of a single project, cPanel gives you two powerful tools: addon domains and subdomains. While they sound similar, they serve very different purposes, and choosing the wrong one can lead to confusing site structures, broken links, and unnecessary complexity. This guide walks through exactly when to use each option and how to configure them correctly inside cPanel.
Addon Domains vs Subdomains: Understanding the Difference
An addon domain lets you host a completely separate website under a different domain name, all from the same cPanel account. For example, if your main site is example.com, you can add anothersite.com as an addon domain. Visitors see it as an independent website — it gets its own document root, its own email accounts, and its own databases.
A subdomain, by contrast, is a subdivision of your primary domain. It uses the format subdomain.example.com and points to a subdirectory within your main account’s file structure. Subdomains are ideal for separating content areas of the same site, like blog.example.com, shop.example.com, or docs.example.com.
The table below highlights the key differences at a glance:
| Feature | Addon Domain | Subdomain |
|---|---|---|
| Domain format | Separate registered domain | Prefix of your primary domain |
| Appearance to visitors | Fully independent website | Section of your main site |
| Document root | Dedicated folder | Subfolder of main document root |
| Email accounts | Independent email addresses | Shares primary domain email |
| DNS management | Requires nameserver changes | Managed entirely within cPanel |
| Best for | Multiple distinct brands or projects | Organizing content areas |
How to Set Up Addon Domains in cPanel
Before you begin, make sure you own the domain you want to add and that its nameservers point to your hosting provider. Without correct DNS delegation, the domain won’t resolve to your server.
Step 1: Navigate to the Addon Domains Interface
Log in to your cPanel dashboard and scroll down to the Domains section. Click Addon Domains. You’ll see a form asking for the new domain name and some folder preferences.
Step 2: Enter the Domain and Set the Document Root
Type the full domain name (e.g., anothersite.com) into the first field. cPanel will automatically suggest a document root path like /home/username/public_html/anothersite.com. You can customize this if needed — just make sure it’s a directory that doesn’t already contain important files. The document root is where you’ll upload that domain’s website files.
Step 3: Create a Password (Optional)
cPanel may prompt you to set an FTP password for the addon domain. If you plan to manage files through the File Manager or SFTP with your main account credentials, you can skip this step. If you’re giving someone else access to upload files for this domain only, set a dedicated password here.
Step 4: Click Add Domain
After clicking the button, cPanel creates the new document root directory and sets up the Apache virtual host entry. Within seconds, the domain is ready to serve content — assuming DNS has propagated. DNS changes can take anywhere from a few minutes to 48 hours depending on your domain’s TTL settings.
How to Create Subdomains in cPanel
Subdomains are simpler to set up because they don’t require external DNS changes. Everything happens within your existing cPanel account.
Step 1: Open the Subdomains Tool
In the same Domains section of cPanel, click Subdomains. You’ll see a form with a single text field for the subdomain prefix and a dropdown for the primary domain.
Step 2: Choose a Prefix and Document Root
Enter the prefix — for example, type blog to create blog.example.com. cPanel will suggest a document root like /home/username/public_html/blog. You can change this to point to any directory on your account. This is useful if you want your subdomain to serve files from a non-standard location.
Step 3: Create the Subdomain
Click Create. cPanel adds a DNS A record for the subdomain pointing to your server IP, creates the document root directory, and updates the Apache configuration. Unlike addon domains, the subdomain is accessible immediately because the DNS record is managed by your hosting provider’s nameservers.
Managing DNS Records for Addon Domains and Subdomains
Once you’ve created an addon domain or subdomain, you may need to fine-tune its DNS settings. cPanel’s Zone Editor (also under the Domains section) gives you full control over DNS records.
For addon domains, verify that the following records exist:
- A record — points the domain to your server’s IP address
- MX record — routes email for the domain (if you plan to use email)
- CNAME record — for www subdomain resolution
For subdomains, cPanel automatically creates the necessary A record. However, if your site uses a third-party service like Cloudflare or a CDN, you may need to add a CNAME record in your external DNS panel. In that case, point the subdomain to the CDN provider’s endpoint rather than your server’s IP.
A common mistake is forgetting to update nameservers before adding an addon domain. If the domain’s current nameservers still point to a different host, visitors will never reach your cPanel server. Use a tool like dig +short example.com ns from the command line to check current nameservers before troubleshooting other issues.
Common Pitfalls and How to Avoid Them
Document Root Conflicts
If you set the document root of an addon domain or subdomain to a directory that already contains files from another site, you’ll get mixed content or a broken site. Always create a fresh, empty directory for each new domain or subdomain.
SSL Certificate Gaps
AutoSSL in cPanel covers your primary domain and often addon domains, but subdomains sometimes slip through the cracks. After creating a subdomain, visit SSL/TLS Status in cPanel and click Run AutoSSL for that subdomain to ensure it gets a valid Let’s Encrypt certificate. Without HTTPS, browsers will mark the subdomain as “Not Secure.”
Redirect Loops
If you set up a redirect from your primary domain to an addon domain (or vice versa), double-check that you’re not creating a circular redirect. This happens more often than you’d think and can be diagnosed by viewing the redirect rules in cPanel’s Redirects tool.
Resource Limits
Each addon domain and subdomain consumes resources on your hosting account — disk space, inodes, and process limits. Check your hosting plan’s terms to understand how many addon domains are allowed. Shared hosting plans typically cap addon domains at 5 to 10, while VPS plans are far more generous.
Key Takeaways
- Use addon domains for completely separate websites under different domain names; use subdomains for organizing content areas under your primary domain.
- Always verify that addon domain nameservers point to your hosting provider before adding them in cPanel.
- Subdomains are instant because cPanel manages DNS internally — no external propagation required.
- Run AutoSSL after creating any new domain or subdomain to avoid “Not Secure” browser warnings.
- Use unique, empty directories for each document root to prevent file conflicts.
- Monitor your hosting plan’s addon domain limits to avoid hitting resource caps.