cPanel Parked Domains: Point Multiple Domains to One Site

If you've picked up a couple of domain variations - the .com, the .in, maybe an old brand name you don't want a competitor grabbing - and you want them all to land on the same website, cPanel's parked domain feature does exactly that. It's one of the most misunderstood parts of cPanel, mostly because the interface changed a few years back and a lot of guides online still describe the old menu. Here's what a parked domain actually does, how to set one up correctly, and the fixes for the two problems that trip people up every time.

What a Parked Domain Actually Is

A parked domain (cPanel calls it a "domain alias" internally) is a second domain name that points to the exact same content as your primary domain or an existing addon domain. It doesn't get its own public_html folder. There's no separate file structure to manage - it's purely a DNS-and-webserver-config trick that tells Apache or LiteSpeed "when a visitor asks for this hostname, serve them whatever's already in this account's document root."

That's the whole point of parking a domain: zero extra hosting overhead, one set of files to maintain, and every domain you own shows the same site.

Parked Domain vs Addon Domain vs a Redirect

These three get confused constantly because they all "connect a domain to your hosting," but they behave very differently:

If you want visitors to actually stay on the parked domain's URL while seeing your main site's content, you want parking. If you want them redirected to the primary domain's URL in the address bar, that's a 301 redirect instead, not a parked domain.

How to Add a Parked Domain in Current cPanel

Since cPanel version 78 or so, Addon Domains, Parked Domains, and Subdomains all live under one unified Domains interface, which is why some people can't find "Parked Domains" as a separate icon anymore - it's not gone, it's merged in.

1. Point the DNS first. The domain needs an A record pointing at your server's IP, or its nameservers need to be the same ones your primary domain uses. Do this before touching cPanel - propagation takes time and you don't want to debug a DNS problem while thinking cPanel is broken.
2. Log in to cPanel and open Domains.
3. Click Create A New Domain.
4. Type the domain name (no www., no trailing slash).
5. Look for the checkbox labeled something like "Share document root (public_html) with another domain". Check it, then pick the domain whose content you want it to mirror.
6. Click Submit.

Leaving that checkbox unticked instead creates a full addon domain with its own folder - so that one checkbox is the entire difference between "parked domain" and "addon domain" in the current UI.

On a few older WHM/cPanel builds you'll still see a standalone Aliases icon that does the same job under its old name - functionally identical, just an older label.

Symptom: The Parked Domain Shows a Default cPanel Page or the Wrong Site

Cause: almost always DNS, not cPanel. Either the A record hasn't propagated yet, it's pointing at the wrong IP, or your local resolver has an old answer cached.

Fix: check what the domain is actually resolving to before assuming the parking is broken:

dig +short yourdomain.com A
dig +short yourdomain.com NS

Compare the IP against your server's real IP (found in WHM's home page or cPanel > General Information). If it doesn't match yet, the parking config is fine - you're just waiting on DNS. Give it up to 24-48 hours, though most resolvers pick it up within a couple of hours.

Symptom: "Not Secure" Warning or SSL Error on the Parked Domain

Cause: AutoSSL issues one certificate that covers a domain and its parked/addon domains, but it only picks up a newly parked domain on its next scheduled run - not the instant you click Submit. Until then, the domain is served with whatever certificate was already active (usually the primary domain's), and browsers reject it because the hostname doesn't match.

Fix: force an immediate recheck instead of waiting for the next cron cycle:

• In WHM, go to SSL/TLS Status, select the account, and click Run AutoSSL.
• From cPanel itself, open SSL/TLS Status and click Run AutoSSL for the domain.

Give it a few minutes, then reload the site in an incognito window (regular windows love to cache the old cert warning). If it's still failing after a run, double check DNS is actually resolving to your server - AutoSSL can't validate domain ownership over HTTP if the domain isn't pointing here yet.

Serving Slightly Different Content Without Making It a Full Addon Domain

Sometimes you want a parked domain to show almost the same site but swap out one thing - a different logo, a different default page - without the overhead of a full addon domain and its own database. You can do this with a host-based rewrite in the primary domain's .htaccess:

RewriteEngine On
RewriteCond %{HTTP_HOST} ^(www\.)?parkeddomain\.com$ [NC]
RewriteRule ^$ /parked-landing.html [L]

That checks which hostname the visitor actually typed and serves a specific file only for that domain, while everything else still falls through to the normal site. It's a reasonable middle ground, but if you're doing this for more than one page, an addon domain is genuinely simpler to maintain.

Removing a Parked Domain Safely

Go to Domains, find the entry, and click Manage then Remove (or the trash icon next to it in older layouts). This only removes the DNS zone entry and Apache/LiteSpeed vhost config for that hostname - it does not touch any files in public_html, since the parked domain never had its own files to begin with. Your primary site is unaffected.

Prevention Checklist

• Point DNS before creating the parked domain in cPanel, not after - it saves a round of "is it broken" troubleshooting.
• Run AutoSSL manually right after parking a domain instead of waiting for the daily cron.
• Keep a note of which domains are parked vs addon vs redirected - six months later it's easy to forget which is which.
• If SEO matters, remember search engines can flag identical content on multiple domains as duplicate content - a canonical tag pointing at your primary domain avoids any ambiguity.