Hosting multiple websites on a single cPanel account is one of the most powerful features the platform offers, and it’s made possible through addon domains. Whether you’re a developer managing client sites, a small business owner expanding your online presence, or a reseller testing new projects, addon domains let you run completely separate websites \u2014 each with its own domain name, content, and visitors \u2014 all from one hosting account and one control panel.<\/p>\n
<\/p>\n
Unlike subdomains (which are extensions of your primary domain like store.yourprimarysite.com), an addon domain functions as an entirely independent website. Visitors see yoursecondsite.com in their browser bar, and the files, email accounts, and databases powering it live in a dedicated directory under your cPanel account. This guide walks through everything you need to know: how to create an addon domain, how the underlying folder structure works, how to manage email and databases for each domain, and how to troubleshoot the most common issues that arise.<\/p>\n
Before creating an addon domain, it helps to understand what happens behind the scenes. When you add an addon domain, cPanel performs several automated tasks:<\/p>\n
public_html\/addondomain.com<\/code> or public_html\/secondarysite<\/code> (you can customize this path)<\/li>\n- Sets up Apache virtual host entries<\/strong> so the web server knows to serve files from this folder when a visitor requests your new domain<\/li>\n
- Creates a subdomain<\/strong> \u2014 internally, cPanel treats addon domains as parked subdomains of your primary domain (e.g.,
addondomain.yourprimary.com<\/code>)<\/li>\n- Optionally creates an FTP account<\/strong> so you can upload files directly to the addon domain’s folder<\/li>\n<\/ol>\n
Your primary domain’s files stay in public_html\/<\/code>, and each addon domain gets its own folder inside or alongside it. This separation is what makes addon domains genuinely independent \u2014 nothing in your primary site’s directory structure interferes with the addon domain’s files.<\/p>\nAddon Domains vs. Parked Domains vs. Subdomains<\/h3>\n
These three features are often confused. Here is the distinction:<\/p>\n
\n- Addon Domain:<\/strong> A completely new website with its own domain name, content, and folder. Example: You have
myhosting.com<\/code> and add myclientsite.com<\/code> as a standalone site.<\/li>\n- Parked Domain (Alias):<\/strong> An additional domain name that shows the exact same content as your primary domain. Example: You own both
myhosting.com<\/code> and myhosting.net<\/code> \u2014 both display identical content.<\/li>\n- Subdomain:<\/strong> A prefix of your primary domain pointing to a subfolder. Example:
blog.myhosting.com<\/code> serves files from public_html\/blog\/<\/code>.<\/li>\n<\/ul>\nStep-by-Step: How to Create an Addon Domain in cPanel<\/h2>\n
Follow these instructions to add a new domain to your cPanel account. You will need the domain name already registered and pointing to your server’s nameservers \u2014 or at least have an A record pointing to your hosting IP address.<\/p>\n
\n- Log into cPanel<\/strong> using your hosting provider’s login link (typically
https:\/\/yourdomain.com\/cpanel<\/code> or https:\/\/yourdomain.com:2083<\/code>).<\/li>\n- Navigate to “Domains” or “Addon Domains”<\/strong> under the Domains section of the cPanel dashboard. In newer cPanel versions (v98+), look for the “Domains” icon directly.<\/li>\n
- Enter the new domain name<\/strong> in the “Create a New Domain” field. Type it without
www<\/code> \u2014 cPanel handles www automatically.<\/li>\n- Set the document root<\/strong> (optional but recommended). cPanel auto-fills
public_html\/yourdomain.com<\/code>. You can change this if you prefer a shorter path like public_html\/site2<\/code>. Write this path down \u2014 you will upload your site files here.<\/li>\n- Create an associated FTP account<\/strong> (optional). If you plan to let someone else manage files for this site (a client or freelancer), check “Create an FTP account” and set a username and password. This gives them access only to this addon domain’s folder, not your primary domain.<\/li>\n
- Click “Submit” or “Add Domain.”<\/strong> After a few seconds, cPanel confirms the addon domain is created and shows the document root path.<\/li>\n<\/ol>\n
Once created, your addon domain is immediately accessible if DNS has propagated. Upload your website files to the document root folder using cPanel’s File Manager or an FTP client.<\/p>\n
Managing Email and Databases for Addon Domains<\/h2>\n
Each addon domain can have its own email accounts, databases, and subdomains \u2014 just like your primary domain.<\/p>\n
Setting Up Email for an Addon Domain<\/h3>\n
To create email accounts for your addon domain:<\/p>\n
\n- Go to Email \u2192 Email Accounts<\/strong> in cPanel.<\/li>\n
- From the domain dropdown, select your addon domain instead of the primary domain.<\/li>\n
- Enter the desired email prefix (e.g.,
info<\/code>), set a password, and choose a storage quota.<\/li>\n- Click Create Account<\/strong>.<\/li>\n<\/ol>\n
Emails like info@addondomain.com<\/code> now work independently from your primary domain’s email. MX records, SPF, DKIM, and DMARC settings for the addon domain can be managed separately through the Zone Editor<\/strong> \u2014 though in most shared hosting setups, these are inherited from the mail server configuration.<\/p>\nCreating Databases for an Addon Domain<\/h3>\n
If your addon domain runs a CMS like WordPress, you need a dedicated database:<\/p>\n
\n- Open Databases \u2192 MySQL Databases<\/strong>.<\/li>\n
- Create a new database (name it something recognizable, like
addonsite_wp<\/code>).<\/li>\n- Create a new database user and assign it to the database with all privileges.<\/li>\n
- Note the database name, username, and password \u2014 you need these during the CMS installation.<\/li>\n<\/ol>\n
When installing WordPress or another CMS on your addon domain, use these database credentials during setup. The site files go in the addon domain’s document root, and the CMS stores its data in this database.<\/p>\n
Common Addon Domain Issues and How to Fix Them<\/h2>\n
Even though cPanel makes addon domain setup straightforward, a few problems crop up regularly. Here is how to diagnose and fix the most common ones.<\/p>\n
“Domain is already configured” Error<\/h3>\n
If you see this, the domain may already exist as a parked domain, subdomain, or addon domain in your account. Check under Domains<\/strong> in cPanel to see a complete list. If the domain was recently deleted, DNS cache or Apache configuration files may still reference it \u2014 wait 15\u201330 minutes or contact your hosting provider to clear cached Apache configs.<\/p>\nAddon Domain Shows the Primary Domain’s Content<\/h3>\n
This usually means DNS has resolved correctly, but the addon domain’s document root is either empty or the Apache virtual host entry is not pointing to the right folder. Verify:<\/p>\n
\n- The document root path under Domains \u2192 your addon domain<\/strong> matches where you actually uploaded your site files.<\/li>\n
- The folder contains an
index.php<\/code> or index.html<\/code> file.<\/li>\n- File permissions on the folder are set to
755<\/code> and files to 644<\/code>.<\/li>\n<\/ul>\n“500 Internal Server Error” After Creating an Addon Domain<\/h3>\n
A 500 error typically points to a permissions issue or a misconfigured .htaccess<\/code> file in the addon domain’s folder. Check the addon domain’s public_html\/addondomain.com\/.htaccess<\/code> file \u2014 if it contains rules meant for the primary domain, they may not apply correctly. Temporarily rename the .htaccess<\/code> file to see if the error clears, then regenerate it for the specific CMS you are running.<\/p>\nBest Practices for Managing Multiple Addon Domains<\/h2>\n
If you run several addon domains, these practices will keep things manageable:<\/p>\n
\n- Use consistent folder naming.<\/strong> Stick with
public_html\/domainname.com<\/code> so you always know where each site’s files live.<\/li>\n- Create separate FTP accounts.<\/strong> For client sites, always use per-domain FTP accounts \u2014 never share your primary cPanel credentials. This limits access to exactly one site.<\/li>\n
- Monitor resource usage.<\/strong> Each addon domain consumes disk space, inodes, CPU, and memory. cPanel’s Resource Usage<\/strong> section shows per-domain statistics. If one addon domain spikes traffic, it can affect all other sites on the account.<\/li>\n
- Keep CMS installations updated.<\/strong> An outdated WordPress install on one addon domain can compromise your entire cPanel account through cross-site vulnerabilities. Set up automatic updates or schedule regular maintenance checks.<\/li>\n
- Back up regularly.<\/strong> Most cPanel hosting providers offer partial backup options \u2014 you can download a single addon domain’s home directory and its associated databases independently of your primary site.<\/li>\n<\/ul>\n
Key Takeaways<\/h2>\n\n- Addon domains let you host multiple independent websites under one cPanel account, each with its own domain, files, email, and databases.<\/li>\n
- Creation involves cPanel setting up a document root folder, Apache virtual host entry, and internal subdomain \u2014 all automatically.<\/li>\n
- Email accounts and MySQL databases for each addon domain are managed separately from the primary domain through cPanel’s standard tools.<\/li>\n
- Common issues like wrong document root paths, DNS propagation delays, and .htaccess conflicts can be diagnosed and fixed with a few checks.<\/li>\n
- Best practices include consistent folder naming, separate FTP accounts per site, monitoring resource usage, and keeping CMS installs updated across all addon domains.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"
Learn how to create and manage addon domains in cPanel. Step-by-step guide covering setup, email, databases, and troubleshooting for hosting multiple websites.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[99],"tags":[101,321,100,255,320],"class_list":["post-130","post","type-post","status-publish","format-standard","hentry","category-domain-management","tag-addon-domains","tag-cpanel-addon-domain-guide","tag-cpanel-domain-management","tag-domain-management","tag-multiple-websites-cpanel"],"_links":{"self":[{"href":"https:\/\/cpanelreview.com\/index.php\/wp-json\/wp\/v2\/posts\/130","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cpanelreview.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cpanelreview.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cpanelreview.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cpanelreview.com\/index.php\/wp-json\/wp\/v2\/comments?post=130"}],"version-history":[{"count":0,"href":"https:\/\/cpanelreview.com\/index.php\/wp-json\/wp\/v2\/posts\/130\/revisions"}],"wp:attachment":[{"href":"https:\/\/cpanelreview.com\/index.php\/wp-json\/wp\/v2\/media?parent=130"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cpanelreview.com\/index.php\/wp-json\/wp\/v2\/categories?post=130"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cpanelreview.com\/index.php\/wp-json\/wp\/v2\/tags?post=130"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}