Addon Domains, Parked Domains and Subdomains in cPanel

cPanel lets you host multiple sites on one account using three different “domain types”: addon, parked (alias), and subdomain. They look similar in the menu but do very different things. Picking the wrong one creates confusion later — addon when you wanted parked means you have two separate sites instead of one site at two URLs. This guide explains what each one does and when to use it.

The three types at a glance

Subdomains

A subdomain is a child of your main domain. blog.yourdomain.com, shop.yourdomain.com, app.yourdomain.com are all subdomains. Each gets its own folder in your file system and can serve completely different content from the main domain.

Creating a subdomain

1. cPanel → Domains → Domains (newer cPanel) or Subdomains (older).
2. Click Create A New Domain or Create A Subdomain.
3. Subdomain: e.g. blog.
4. Domain: pick your main domain from dropdown.
5. Document Root: auto-filled to public_html/blog/; usually leave default.
6. Create.

Within minutes the subdomain is live. Files in public_html/blog/ serve at blog.yourdomain.com. AutoSSL issues an SSL cert automatically.

Subdomain use cases

• WordPress blog separate from main site: blog.yourdomain.com.
• Development / staging: dev.yourdomain.com or staging.yourdomain.com.
• App distinct from marketing site: app.yourdomain.com (a SaaS, dashboard, login portal).
• Mail subdomain: mail.yourdomain.com (for mail server addressing, especially when Cloudflare is in front of the main domain).
• API endpoint: api.yourdomain.com.

Addon domains

An addon domain is a completely separate domain hosted on your cPanel account. secondsite.com, thirdsite.com — each looks and feels like an independent website but shares your hosting resources.

Prerequisites

• You own the domain (registered somewhere — could be us or any other registrar).
• Domain’s nameservers point to iWebVault (so our DNS knows about it) OR domain’s DNS has an A record pointing at your server IP.
• Your plan permits addon domains. Most plans allow several; some basic plans cap at one or zero.

Adding an addon domain

1. cPanel → Domains → Domains → Create A New Domain.
2. Domain: enter the new domain (secondsite.com).
3. Subdomain / Document Root: auto-suggested as public_html/secondsite.com/. Generally leave as default.
4. Optionally tick “Share document root with main domain” — but usually you do NOT want this; addon should have its own folder.
5. Create.

Files in the addon’s folder serve at the new domain. AutoSSL issues SSL automatically once DNS is pointing here.

Addon domain quirks to know

• cPanel creates an FTP-style subdomain too: the addon becomes accessible at addondomain.yourmaindomain.com as well. Mostly harmless; can be disabled if desired.
• Shared resources: all addon domains share the SAME resource limits as your main domain (one cPanel account = one resource bucket). Heavy traffic on an addon affects the main and vice versa.
• Shared compromise risk: if one site gets hacked, attackers can typically pivot to others in the same account. Strong passwords on all, keep apps updated everywhere.
• Email: each addon can have its own email accounts (user@addondomain.com) configured via the standard Email Accounts UI.

Parked / Alias domains

A parked domain (now usually called “Alias” in newer cPanel) makes a second domain show the SAME content as your main domain. Useful when you own multiple TLDs of your brand and want them all to land on the same site.

Setting up an alias

1. Point the alias domain’s DNS to iWebVault (nameservers or A record).
2. cPanel → Domains → Aliases (older: Parked Domains).
3. Create Domain — enter the alias domain.

Now aliasdomain.com serves the same content as yourmaindomain.com. Both URLs resolve to identical pages.

SEO consideration

Having identical content at two URLs is duplicate content — search engines may rank one and ignore the other, or split the ranking signal between them. Best practice:

• Pick one as the canonical domain.
• 301-redirect the alias to the canonical, instead of using a true alias.

Use Aliases when you genuinely want both URLs to work without redirecting (rare). For “I own multiple TLDs of my brand and want them all to go to my site”, use redirects instead. See redirects guide.

Picking the right type

• “I want to add /blog to my main site as a separate WordPress install” → Subdomain (blog.yourdomain.com) or a subfolder of the main site.
• “I have a new company / client and want to host their separate website here” → Addon domain.
• “I bought yourdomain.net and yourdomain.org to protect my brand; both should land on my main yourdomain.com” → Redirects (preferred) or Alias.
• “I’m running a dev/staging version of my main site” → Subdomain.
• “I have api.yourdomain.com pointing to a separate service” → Subdomain.

Common multi-site issues

“Addon domain shows my main site instead of its own content.” Likely the addon’s folder is empty or it’s misconfigured. cPanel → Domains → check the document root. Add files there.

“Addon domain has SSL issues.” AutoSSL needs DNS pointing here. Verify DNS, run AutoSSL. SSL troubleshooting.

“I deleted an addon — files are still in the folder.” Removing the addon from cPanel removes the routing but not the files. Delete the folder manually if you don’t need the content.

“My addon domain is hitting resource limits — should I upgrade?” Possibly, but first see if the addon could move to its own cPanel account or VPS. Multiple high-traffic sites on one shared account is the common cause of plan-busting resource use.

“Can I have an addon domain that’s also a registered domain at iWebVault?” Yes. The registration and the hosting are independent. You can register a domain with us and then add it as an addon to your hosting (or any other host).

Limits and plan considerations

Plans have caps on number of addons/aliases. Check your plan details for specifics. Hitting the cap:

• Upgrade to a higher tier with more allowed.
• Move the addon to its own cPanel account (better isolation).
• Consolidate if multiple addons are for one project.

What’s next

• Redirects (often better than aliases): Redirect guide.
• SSL for additional domains: SSL/AutoSSL.
• DNS basics needed when pointing new domains: DNS records explained.

Subdomain for “parts of one site”. Addon for “different sites under one account”. Alias for “same content multiple URLs” — though redirects usually serve that purpose better. Match type to intent and the rest is configuration.