---
title: Addon Domains
description: Extra domains on the same hosting account. One plan, multiple sites — with separate document roots, email options, and shared resource limits to understand.
canonical: https://penasihathosting.com/en/hosting-wiki/addon-domains
type: wiki
locale: en
updated: 2026-07-15
author: Willya Randika
---

# Addon Domains

## Overview

- **Summary:** Extra domains on the same hosting account. One plan, multiple sites — with separate document roots, email options, and shared resource limits to understand.
- **Author:** Willya Randika ([profile](/penulis/willya-randika))

## Article

**Addon domain** (sometimes labeled simply as an extra domain) lets you run another domain on the **same hosting account** as your primary site. Each domain can have its own website files, its own document root, and usually its own email — while still sharing the account’s disk, [bandwidth](/en/hosting-wiki/hosting-bandwidth), [inodes](/en/hosting-wiki/inode), and CPU.

You will see this most often on [cPanel](/en/hosting-wiki/cpanel) shared hosting. Other panels use different names, but the idea is the same: multiple domains, one plan.

## A Simple Analogy

Think of the hosting account as a house on one utility meter. The primary domain is the main house. An addon domain is another building on the same lot with a **different street address**.

Visitors to address B do not automatically walk into address A’s living room — but if the shared power (resources) runs out, every building feels it.

## How It Works

When someone visits an addon domain:

1. That domain’s [DNS](/en/hosting-wiki/dns-domain-name-system) points at your hosting server  
2. The server matches the hostname (virtual host)  
3. The request is mapped to a **document root** folder for that domain  
4. Files in that folder are what visitors see  

In cPanel, adding an addon domain typically also creates:

- A new document root folder  
- An internal technical subdomain (often invisible in day-to-day use)  
- The option to create mailboxes for that domain  

Point the domain’s nameservers or A record at the hosting server before you judge the result in a browser.

## Addon vs Parked/Alias vs Subdomain

| Type | What it does | Common use |
| --- | --- | --- |
| **Addon domain** | Separate site in its own folder | Another brand or project on one account |
| **Parked / alias domain** | Shows the primary site’s content | Backup domains, typos, brand aliases |
| **Subdomain** | Prefix on an existing domain (`blog.example.com`) | Staging, apps, site sections |

If you only want `newbrand.com` to show the same site as the primary domain, you usually need an **alias/parked domain** or a redirect — not a full addon.

## Benefits and Limits

**Benefits**

- One hosting bill for several small sites  
- Email per domain (`name@otherbrand.com`)  
- Cleaner file separation than dumping every project in one folder  

**Limits**

- Resources are **still shared** — one heavy site can starve the others  
- Providers often cap how many addon domains you get  
- Backups, SSL, and CMS updates remain **per site**  
- Busy traffic or strict isolation is healthier on a [VPS](/en/unmanaged-vps) or separate accounts  

## Quick Setup in cPanel

Typical flow (labels vary slightly):

1. Sign in to [cPanel](/en/hosting-wiki/cpanel)  
2. Open **Domains** / **Addon Domains**  
3. Enter the new domain name  
4. Set or accept the document root  
5. Save, then confirm DNS points at the server  
6. Issue [SSL/TLS](/en/hosting-wiki/ssl-tls) (often Let’s Encrypt) for that domain  
7. Upload files or install a CMS into the document root  

<Callout type="warning">
  If DNS has not finished updating, the domain will not “go live” even though the panel already lists it. Check [domain propagation](/en/hosting-wiki/domain-propagation) when results differ by network or device.
</Callout>

## What to Watch For

- **Multi-site on shared is not full isolation** — your other sites on the account are noisy neighbors to each other  
- **Watch disk and inodes** — multiple CMS installs, caches, and mailboxes burn [inodes](/en/hosting-wiki/inode) quickly  
- **SSL is per domain** — HTTPS on domain A does not automatically cover domain B  
- **Tighten FTP when needed** — create [FTP/SFTP](/en/hosting-wiki/ftp-sftp) users limited to the addon folder, not the whole home directory  
- **Read the provider’s terms** — some plans discourage “stealth reselling” or too many production businesses on one shared account  

## FAQ

<Accordion>
  <AccordionItem title="How many addon domains can I create?">
    It depends on the plan. Some allow one or two; others advertise “unlimited” under a fair-use policy. Check the plan specs or ask support before moving many sites onto one account.
  </AccordionItem>
  <AccordionItem title="Will an addon domain slow my main site down?">
    Not by itself. Total load matters: traffic, heavy scripts, and account limits. Two light sites are usually fine; a plugin-heavy WordPress shop plus another busy CMS on the same account is a common source of pain.
  </AccordionItem>
  <AccordionItem title="Addon domain or separate hosting?">
    Use addons for smaller, lower-risk sites. Split hosting (or move up to a VPS) when you need stronger isolation, more predictable performance, or separate clients/teams that should not affect each other.
  </AccordionItem>
  <AccordionItem title="Why do I still see the default hosting page?">
    Usually DNS is wrong or still propagating, the document root is empty, or you tested too early. Confirm files are in the right folder and that DNS/SSL have settled.
  </AccordionItem>
  <AccordionItem title="Does primary-domain email automatically work on the addon domain?">
    No. Create mailboxes or forwarders for the addon domain under Email accounts. [SMTP](/en/hosting-wiki/smtp)/IMAP settings follow that domain.
  </AccordionItem>
</Accordion>