Addon Domain cPanel: 7 Steps That Actually Work for Beginners

An addon domain lets you host multiple websites under a single cPanel hosting account. You pay for one hosting plan, point a separate domain name to it, and cPanel creates the folders, DNS records, and subdomain structure automatically. It's the most common way to run five or ten unrelated sites without buying five separate hosting subscriptions.

But the cPanel wizard can be confusing the first time. You see fields for "subdomain" and "document root" that aren't explained anywhere, and sometimes the new domain shows a blank page or a 404 even after you finish the form. This checklist walks you through every field, explains what each one does, and shows you how to verify the setup worked.

What is an addon domain and why does cPanel need one

Your cPanel account starts with one primary domain—the domain you chose when you signed up. That domain points to the public_html folder. An addon domain is any additional domain name you attach to the same account. cPanel will:

• Create a subdomain of your primary domain (for internal routing).
• Create a new folder inside public_html to hold the addon domain's files.
• Add DNS zone records (if your nameservers point to the cPanel server).
• Configure Apache or LiteSpeed to serve the new domain from that folder.

You can add as many addon domains as your hosting plan allows. Shared hosting plans often cap this at ten or twenty-five; reseller and VPS plans typically allow unlimited.

Addon domain vs parked domain vs subdomain

These three terms trip people up constantly.

• Addon domain: a completely separate website with its own domain name and its own folder. example.com shows site A; mystore.net shows site B.
• Parked domain (alias): points to the same content as your primary domain. example.org and example.com both show the exact same site, served from public_html.
• Subdomain: a prefix under your existing domain. blog.example.com lives in a separate folder but shares the parent domain.

If you want a new, independent site, you want an addon domain.

Before you start: domain and DNS prerequisites

You must own or control the domain name you plan to add. Register it at any domain registrar (Namecheap, GoDaddy, Cloudflare Registrar, your hosting provider). The domain does not have to be registered with the same company that provides your cPanel hosting.

Next, decide who will manage DNS. You have two choices:

1. Point the domain's nameservers to your cPanel host (e.g., ns1.yourhost.com, ns2.yourhost.com). cPanel will create the DNS zone and A records automatically when you add the addon domain.
2. Keep the domain's nameservers at the registrar or at Cloudflare, and manually create an A record pointing to your cPanel server's IP address.

Option one is simpler for beginners because cPanel handles DNS for you. Option two gives you more control and is necessary if you use Cloudflare's proxy or want to keep email DNS separate.

Find your cPanel server's IP address in the cPanel sidebar under "Server Information" or "Shared IP Address." Write it down; you may need it.

Step-by-step: adding your first addon domain

Log into cPanel. In the Domains section (older cPanel themes call it "Domains" or "Addon Domains"), click Domains (newer cPanel) or Addon Domains (older interface). Both buttons do the same thing.

Step 1: Enter the new domain name

In the Domain field, type the full domain exactly as you registered it: mynewsite.com. Do not include http:// or www. If you want www.mynewsite.com to work, you only need to enter mynewsite.com—cPanel creates a www alias automatically.

Press Tab or click into the next field. cPanel will auto-fill the subdomain and document root based on the domain you typed.

Step 2: Check the subdomain field

cPanel creates a subdomain of your primary domain as a behind-the-scenes identifier. If your primary domain is mainsite.com and you add mynewsite.com, cPanel suggests a subdomain like mynewsite.mainsite.com.

You will almost never visit this subdomain, and visitors will never see it. It exists for cPanel's internal routing and for FTP access in some configurations. The auto-filled value is fine. Leave it as-is unless you have a specific reason to change it (you won't).

Step 3: Confirm the document root

The Document Root is the folder where your new site's files live. cPanel suggests public_html/mynewsite.com (or sometimes just mynewsite.com if your host's configuration hides the public_html prefix in the interface).

This is correct. Each addon domain gets its own folder so files don't collide. You'll upload your WordPress installation, HTML files, or application code into this folder later.

If you change the document root to something like public_html/store, cPanel will create that folder instead. Custom paths are fine, but stick with the default unless you have a folder-naming convention you already follow.

Step 4: Uncheck "Create an FTP account"

You'll see a checkbox offering to create a dedicated FTP account for the new domain. This is optional and most people don't need it. Your main cPanel username can already access every folder, including the new addon domain's folder.

Uncheck this box unless you want to give a designer or contractor access to only this one site and nothing else. If you do create the FTP account, cPanel will ask for a username and password in additional fields.

Step 5: Click Add Domain

Hit the Add Domain button. cPanel will spend a few seconds creating:

• The subdomain entry.
• The folder at public_html/mynewsite.com.
• The DNS zone (if nameservers point here).
• The Apache virtual host configuration.

You'll see a success message. The domain is now attached to your account.

What happens behind the scenes

When you added the domain, cPanel modified several configuration files and created a DNS zone. Here's what changed:

Apache virtual host

cPanel wrote a new <VirtualHost> block in Apache's config (or a similar directive for LiteSpeed or NGINX). This block tells the web server: "When a request arrives for mynewsite.com, serve files from /home/username/public_html/mynewsite.com." You never touch this file directly; cPanel regenerates it whenever you add or remove a domain.

DNS zone

If your nameservers point to cPanel, the system created a DNS zone for mynewsite.com with:

• An A record pointing mynewsite.com to your server's IP.
• An A record for www.mynewsite.com pointing to the same IP.
• MX records for mail (if your plan includes email).
• Default TXT records for SPF/DKIM if email is enabled.

You can see and edit this zone under Zone Editor in cPanel.

Subdomain in the primary domain's zone

cPanel also added a subdomain entry (mynewsite.mainsite.com) to your primary domain's DNS zone. This subdomain is mostly invisible but helps cPanel's account structure.

Verify the addon domain is working

Don't assume success just because cPanel said "Domain created." DNS propagation and folder permissions can cause silent failures.

Check 1: Ping the domain

Open a terminal (Mac/Linux) or Command Prompt (Windows) and run:

ping mynewsite.com

You should see replies from your cPanel server's IP address. If you see a different IP or "could not find host," DNS hasn't propagated yet. Wait an hour and try again, or check your nameserver settings at the registrar.

Check 2: Visit the domain in a browser

Go to http://mynewsite.com. You'll see one of three things:

1. cPanel's default "Coming Soon" page or your host's placeholder. This is normal for a brand-new addon domain with an empty folder.
2. Your main site's content (the site from public_html). This means the addon domain's virtual host didn't apply. Restart Apache in WHM or contact support.
3. 404 or directory listing. The domain is working, but the folder is empty or lacks an index.html or index.php.

Scenario 1 or 3 means success. Scenario 2 means something went wrong in the virtual host configuration.

Check 3: Upload a test file

Use the File Manager in cPanel. Navigate to public_html/mynewsite.com and create a new file called index.html with this content:

<!DOCTYPE html>
<html>
<head><title>Test</title></head>
<body><h1>Addon domain works!</h1></body>
</html>

Save it, then visit http://mynewsite.com again. You should see "Addon domain works!" in big letters. If you do, the addon domain is live.

Common mistakes and how to fix them

The domain shows a blank page or my main site

Apache (or LiteSpeed) is serving the wrong document root. Log out of cPanel, log back in, and try removing the addon domain and re-adding it. If that doesn't help, open a ticket with your host—virtual host misconfigurations require root access to debug.

Alternatively, check MultiPHP Manager in cPanel. If the addon domain is listed with a different PHP version than you expected, that won't cause a blank page, but it can cause application errors that look like blank output.

DNS points to the old server or registrar parking page

You didn't update the nameservers, or you updated them but propagation hasn't finished. Go to your domain registrar, find the nameserver settings, and change them to your host's nameservers (ns1.yourhost.com, ns2.yourhost.com). Propagation takes anywhere from ten minutes to forty-eight hours, though most updates finish in under four hours.

Use a tool like dig or an online DNS checker (whatsmydns.net) to see what different DNS servers around the world are returning for your domain.

cPanel says the domain is already configured

The domain might already be a parked domain or an alias. Go to Domains (or Aliases / Parked Domains in older cPanel), remove any entries for mynewsite.com, then try adding it as an addon domain again.

The folder doesn't appear in File Manager

Click the Settings button (gear icon) in File Manager and make sure "Show Hidden Files" is enabled. If you still don't see public_html/mynewsite.com, the addon creation failed silently. Try adding the domain again, and watch for error messages this time. You may have hit the addon domain limit for your plan.

Email for the addon domain doesn't work

Addon domains share the same cPanel account, so email accounts for [email protected] are created the same way as for your primary domain. Go to Email Accounts, choose mynewsite.com from the dropdown, and create the address. MX records are added automatically if your DNS zone is managed in cPanel. If you use external nameservers, you must manually create MX records pointing to your mail server.

Managing addon domains after setup

Once the domain is working, you manage it like any other site in your account.

Installing applications

Most cPanel hosts include Softaculous or Installatron for one-click installs of WordPress, Joomla, PrestaShop, etc. When you run the installer, you'll see a dropdown to choose which domain to install into. Select your addon domain, and the installer will place files in the correct folder and configure the database.

SSL certificates

cPanel's AutoSSL (using Let's Encrypt or Sectigo) automatically provisions SSL certificates for addon domains. Within a few hours of adding the domain, you should see a padlock in your browser when you visit https://mynewsite.com. If AutoSSL fails, check that the domain's A record points to the correct IP and that port 80 is accessible (some firewalls block Let's Encrypt's validation requests).

You can also manually install a certificate under SSL/TLS > Manage SSL Sites.

Removing an addon domain

Go to Domains, find the addon domain in the list, and click Manage or the three-dot menu, then Remove. cPanel will delete the DNS zone, the subdomain entry, and the virtual host configuration. The folder (public_html/mynewsite.com) and all files inside it remain on disk; you must delete them manually if you want them gone.

Quick reference checklist

Print this or keep it in a tab:

1. Register or transfer the domain name.
2. Point nameservers to cPanel host (or create A record if using external DNS).
3. Log into cPanel > Domains > Create A New Domain (or Addon Domains).
4. Enter the full domain name (no http:// or www).
5. Accept the auto-filled subdomain and document root.
6. Uncheck "Create FTP account" unless you need it.
7. Click Add Domain.
8. Wait 10–60 minutes for DNS propagation.
9. Verify with ping and browser visit.
10. Upload a test index.html to confirm folder routing.
11. Install your application or upload site files.
12. Check SSL certificate appears within a few hours.

That's it. Seven form fields, one click, and a short wait.

Where to go when addon domain setup fails

If you followed every step and the domain still doesn't resolve or shows the wrong content, check these before opening a support ticket:

• Confirm nameservers at the registrar match the ones your host provided. Copy-paste errors are common.
• Wait at least four hours after changing nameservers. DNS caching is real.
• Check Error Log in cPanel (under Metrics) for the addon domain. Look for File does not exist or permission errors.
• Verify you didn't hit the addon domain limit. cPanel will reject the request if you're at the cap.
• Check that your account isn't suspended. A suspended account won't serve any domains, addon or primary.

If none of that helps, gather your domain name, the steps you took, and any error messages, then contact your host's support. In support tickets I handled, the usual culprit was either stale DNS cache on the user's local machine (solved by flushing DNS or waiting) or a typo in the domain name field that created a subdomain instead of an addon domain.

Addon domains are simpler than they look. The cPanel wizard does the hard work; you just fill in one field and let DNS propagate.

Related posts

• MX Record Setup: 7 Errors Fixed (Common Mistakes)
• NVMe VPS Hosting: 7 Providers With Real SSD Upgrades
• VPS Hosting vs Shared Hosting: 2026 Cost Breakdown
• Server Security Hardening Checklist: 12 Config Changes