Domains & delegation · Beginner · 10 minutes
Adding an Addon Domain: Two Names, One Account, Two Sets of Records
You have bought a second name and want it serving a different site from the same account — without finding out in a fortnight that its mail, its certificate and its renewal date were never arranged at all.
The short answer
An addon domain is a second registration hosted inside the same cPanel account: the registry still treats it as an entirely separate name, with its own delegation, its own DNS zone, its own certificate and its own expiry date, and only disk space and the account's resources are genuinely shared. Move its nameservers here first, then create it on a document root of its own.
What follows is the order the two systems need — registry first, panel second — the default record that quietly swallows the second name's email, and the naming habit that keeps a five-name account readable a year from now.
By the Hosting & Domains team · Reviewed 18 August 2026
Beginner
Level assumed
5
Stages in the procedure
Free
Cost of asking us
Proven
Where it was checked
No background assumed beyond an account and a browser. Budget 10 minutes. Every instruction is written against our own panel, and anything that belongs to the registry rather than to the host is labelled as such.
One promise before step one: nothing here is a one-way door. Any step that is awkward to reverse is flagged, and the way back is printed beside it.
What the registry sees when you add an addon
Nothing at all. Creating an addon domain in cPanel builds a virtual host and a document root on this server; it does not buy the name, move the registration, renew it, or tell the registry anything whatsoever. The panel will accept a name registered to a stranger without a murmur, so the fact that it saved without an error proves only that the field was well formed.
Keep the two halves separate in your head and most addon-domain confusion disappears: the registry decides which nameservers are authoritative, the nameservers decide what the records say, and the panel decides what happens to a request once it arrives.
Delegation has to land before anything answers
At the registrar holding the second name, point its nameservers at the pair your account uses. The registry publishes that change within minutes, but resolvers around the world keep the previous answer for as long as the old TTL promised — anywhere from an hour to two days. During that window some visitors reach the new site and some reach whatever the name pointed at before.
If you know the move is coming, drop the TTLs on the old zone a day beforehand so the promise has expired everywhere before you change anything. That single piece of preparation turns an anxious evening into a scheduled ten minutes.
The new zone starts empty of every habit you have
Adding a domain here creates a fresh zone with defaults: an A record for the name and for www, and an MX pointing at this server. If the second name's email lives with a third-party provider, that default MX takes delivery instead, and messages stop arriving without a single bounce to warn you. Rebuild the MX set with its priorities, the SPF line and any verification TXT records before you rely on the name for mail.
The same applies to anything a previous host had quietly configured: a CNAME for a help desk, a TXT string proving ownership to an analytics or search tool, a subdomain for a mailing platform. A zone is not inherited; it is rebuilt.
One document root per name, named after the name
Give the addon a document root that is a sibling of public_html rather than a folder inside it. Nested under public_html, the second site also answers at yourdomain.com/otherdomain, which confuses visitors, splits the search signals across two addresses and is entirely avoidable.
Name the folders after the domains — /domain-names/example.com and so on. A year later, an account holding five addons reads either like an index or like an excavation, and that one convention decides which.
Two names, two clocks, two certificates. The addon has its own expiry date, its own auto-renew setting and its own transfer lock, none of which are affected by the parent name's. It also needs its own certificate: AutoSSL only brings a name into reach once that name resolves here, so check the SSL status page after propagation rather than assuming a certificate appeared unprompted.
What is shared is everything else. Resources, security posture and any suspension apply to the whole account, which makes addons excellent for your own projects and unsuitable for a client's livelihood — that is what reseller accounts exist for.
The account these steps were written against
Guides written against imaginary hosting go stale quickly. These are written against the real thing: the same panel, the same zone editor, the same defaults sitting in your account.
NVMe storage and LiteSpeed caching sit under every tier, the smallest included — the floor here rather than something to upgrade towards.
- Checked against the panel your account actually opens
- Registry, registrar and host kept firmly apart
- The trap named before you walk into it
- Someone awake at the hour a record breaks
Why Hosting & Domains
Standard on every plan
Written from the ticket queue
Every trap named here came out of a real support ticket, which is why the awkward ones get named at all.
The clerical half is already done
Certificates issue themselves, the daily copy is taken without being asked, and the records are written when a name is added — so the guide covers only the decisions that are genuinely yours.
Registry, registrar, reseller, host
The four words most guides use interchangeably are kept apart here, because which one you are dealing with decides who can actually fix the problem.
Sized honestly, not flattered
Run a second registration from the same account without losing its records, its certificate or its renewal date is a beginner-level job — set aside 10 minutes, with the steps the platform already absorbs marked as such.
Screens that match the words
Written against the panel your own account opens, so the buttons sit where the page says they sit.
Someone awake when a name breaks
Expiry dates and DNS faults keep no office hours, so the desk answers at whichever hour you find one.
Quick Start
Order placed to site online
- 1
Lower the TTLs the day before
On the zone that currently answers for the second name, drop the record TTLs so cached answers expire quickly. Do this at least a day ahead, because the old, longer value is the one still running.
- 2
Move the delegation at the registrar
Set the name's nameservers to your hosting pair. The registry updates in minutes; resolvers follow over the next one to forty-eight hours depending on the TTLs that were in force beforehand.
- 3
Create the addon on its own document root
From the Domains page, give the name a document root as a sibling of public_html, never a folder inside it, and decline any offer to share a root with an existing site.
- 4
Rebuild the zone before you trust it with mail
Open the zone editor and recreate the MX set with priorities, the SPF line and every verification TXT the name carried elsewhere. The default MX points here, which is wrong for any name whose mailboxes live somewhere else.
- 5
Confirm the certificate, then note what is shared
Once the name resolves here, check the SSL status page rather than assuming. Then record the new expiry date beside the parent's, and remember that resources and any suspension apply to the whole account.
Built In
Fitted to every plan
- A staging copy for rehearsing a change before it goes live
- Webmail in the browser, with IMAP, POP and SMTP for any client
- Spam and virus screening on every mailbox as standard
- Mailboxes answering at the name on your registration
- NVMe SSD storage on every tier, not just the expensive ones
- LiteSpeed caching inside the server, not bolted on by a plugin
- Money back inside 30 days on hosting plans, 7 on reseller
- A renewal figure identical to the one you first registered at
- WordPress Toolkit, with the updates handled for you
- Plan changes applied in place, with no migration to arrange
Frequently Asked
Questions we field again and again
Does hosting a name here move its registration to you?
No. Hosting and registration are separate arrangements, and adding an addon domain touches neither the registrar of record nor the expiry date. The name stays where it is registered, renews on its own schedule and can be transferred later on its own terms — you have simply told this server to answer for it.
The addon resolves but its email has vanished. What happened?
Almost certainly the default MX record in the new zone. Adding a domain here creates a zone that expects mail to be delivered on this server, so if the mailboxes live with another provider their MX records have to be recreated by hand. Open the zone editor, restore the correct MX hosts and priorities, and check the SPF line while you are there.
Can I add a name that is registered somewhere else entirely?
Yes, and it is common. Two routes work: point the name's nameservers here and keep the whole zone in this panel, or leave the zone where it is and publish a single A record aimed at this account's address. The first gives you one place to edit records; the second leaves DNS with your existing provider.
Is a domain registration refundable if I change my mind?
Registrations are not, because the registry charges the moment the name is secured — that fee has already left the building. Hosting is a different matter: shared, business, WordPress and WooCommerce plans carry thirty days, reseller carries seven, and VPS and dedicated servers sit outside the guarantee because they are built to order as soon as payment lands. Inside the window one request returns the hosting fee, with no retention script to sit through.
Keep reading
AI Website Builder
Describe what the name is for and the AI drafts the site on real hosting.
Charity Hosting
Reduced hosting for charities and nonprofits, with nothing essential removed.
Changing provider? Work through this checklist beforehand.
A straightforward running order for a migration your visitors never spot: which files travel first, how to bring the mail across without dropping a single message, the right moment to repoint DNS, and the two errors that sit behind almost every outage we get called in to fix.
Start on a plan whose renewal you can predict.
NVMe hosting with the certificate and the migration included, people answering at any hour, and a figure that stays where it started.
View AI Website Builder plans