Addon domains, subdomains, aliases and redirects.
Contents
- Types of domain in cPanel
- Primary domain (Main Domain)
- Addon domains
- Subdomains
- Domain aliases (Aliases / Parked Domains)
- Adding an addon domain
- Requirements
- Adding an addon domain
- Checking DNS before you add the domain
- Creating a subdomain
- Using subdomains
- Domain aliases
- When to use aliases
- Creating an alias
- Aliases vs redirects
- Redirects
- Types of redirect
- Creating a redirect
- Redirect examples
- Managing redirects
- Advanced redirects through .htaccess
- Managing DNS (Zone Editor)
- Accessing Zone Editor
- Types of DNS record
- Editing DNS records
- Deleting DNS records
- Resetting the DNS zone
- DNS propagation time
- Dynamic DNS
- Usage
- Checking your domain configuration
- Domains Dashboard
- Checking availability
- Troubleshooting
- Limits and quotas
- Moving domains
- Moving a domain to your account
- Moving between accounts
- Best practice
- Solving problems
- Domain already exists
- DNS isn’t updating
- Addon Domain isn’t working
- Subdomains don’t open
- Email doesn’t work after adding a domain
- See also
- External links
The domain management section lets you add addon domains, create subdomains, configure DNS and manage redirects.
Types of domain in cPanel
Primary domain (Main Domain)
- The first domain given when the account was created
- Linked to the
public_htmldirectory - Can’t be deleted (only changed by the hosting provider)
- All other domains are attached to this account
Addon domains
- Full, separate websites on the same account
- Have their own root directory
- Can have their own email accounts
- Count towards the account’s quota
Subdomains
- Subdomains of the primary domain or of addon domains
- Examples:
blog.example.com,shop.example.com - Have their own directory
- Useful for separating different functions
Domain aliases (Aliases / Parked Domains)
- Point to the same content as the primary domain
- Used for different spellings of a domain
- Have no directory of their own
- Example:
example.co.uk→ an alias forexample.com
Adding an addon domain
Requirements
- The domain must be registered
- The domain’s DNS must point to your server
- The account limit must not have been exceeded
Adding an addon domain
- Go to DOMAINS → Domains
- Click Create A New Domain
- Fill in the form:
Settings
- Domain
- Enter the full domain name (for example,
newsite.com)
- Share document root
- The option to use an existing directory
- Off by default — a new folder is created
- Document Root
- The path to the domain’s root directory
- Default:
/home/username/public_html/newsite.com - Can be changed to any path within the account
- Subdomain
- A subdomain is created automatically (optional)
- For example:
newsite.primary-domain.com
- Click Submit
- The domain will be added and activated
Checking DNS before you add the domain
Make sure the domain’s DNS is set up correctly:
- Go to DOMAINS → Track DNS
- Enter your domain
- Check the A record:
- It should point to your server’s IP address
newsite.com → your.server.IP.address
If the DNS isn’t set up:
- Log in to your domain registrar’s control panel
- Change the name servers to those of your hosting provider, or
- Add an A record pointing to the server’s IP
Creating a subdomain
- Go to DOMAINS → Domains
- Click Create A New Domain
- Enter the full subdomain:
Examples:
blog.example.comshop.example.comtest.example.com
Subdomain settings
- Document Root
- The directory for the subdomain’s files
- Default:
/home/username/public_html/subdomain - Example:
/home/username/public_html/blog
- Click Submit
The subdomain will be created and available immediately (if the DNS is set up).
Using subdomains
Typical uses:
| Subdomain | Purpose | Example use |
|---|---|---|
| blog.example.com | Blog | A company WordPress blog |
| shop.example.com | Shop | An online shop |
| forum.example.com | Forum | A user community |
| test.example.com | Testing | A test version of the site |
| api.example.com | API | A REST API for applications |
| cdn.example.com | CDN | Static content |
| m.example.com | Mobile | A mobile version |
Domain aliases
Aliases (also called Parked Domains) send visitors to the primary domain, showing the same content.
When to use aliases
- Different top-level domains:
example.com,example.co.uk,example.net - Common misspellings:
exampl.com - Old brand names
- Brand protection (registering similar domains)
Creating an alias
- Go to DOMAINS → Domains
- Find the primary domain
- Click Manage → Create a New Alias
- Enter the alias domain name
- Click Add Domain
Both domains now show the same content from the same directory.
Aliases vs redirects
| Feature | Alias | Redirect |
|---|---|---|
| URL in the browser | Stays as the alias | Changes to the target domain |
| SEO | Can cause duplicate content | Correct for SEO (301) |
| Use | Alternative domains | Moving a site |
Redirects
Redirects automatically send visitors from one URL to another.
Types of redirect
- 301 (Permanent)
- Permanent redirect
- Used when: moving a site or changing domain
- SEO: passes on link value
- Cached by browsers
- 302 (Temporary)
- Temporary redirect
- Used when: making temporary changes or A/B testing
- SEO: doesn’t pass on link value in full
- Not cached as aggressively
Creating a redirect
- Go to DOMAINS → Redirects
- Click Create a Redirect
- Fill in the settings:
Redirect settings
- Type
- Choose Permanent (301) or Temporary (302)
- Domain
- The source domain (where to redirect from)
- Directory (optional)
- A specific path, or leave empty for the whole domain
- Redirects to
- The destination URL (where to redirect to)
- Can be on the same domain or another one
- www. redirection
- Redirect with or without www. — redirect both versions
- Only redirect with www. — only the www version
- Only redirect without www. — only the version without www
- Do Not Redirect www. — leave www alone
- Wild Card Redirect
- On: redirects all subpages
- Example:
old.com/page→new.com/page - Off: exact matches only
- Click Create
Redirect examples
A whole domain to a new one
- Type: Permanent (301)
- Domain:
old-site.com - Redirects to:
https://new-site.com - Wild Card: Yes
HTTP to HTTPS
- Type: Permanent (301)
- Domain:
http://example.com - Redirects to:
https://example.com - Wild Card: Yes
A specific page
- Type: Permanent (301)
- Domain:
example.com - Directory:
/old-page - Redirects to:
https://example.com/new-page - Wild Card: No
Without www to with www
- Type: Permanent (301)
- Domain:
example.com - Redirects to:
https://www.example.com - www. redirection: Only redirect without www.
Managing redirects
The Current Redirects list shows:
- Type (301/302)
- Source
- Destination
- Actions (Edit, Delete)
Use the corresponding buttons to change or delete a redirect.
Advanced redirects through .htaccess
For complex redirect rules, edit .htaccess:
# Redirect the whole site
Redirect 301 / https://new-site.com/
# Redirect a specific page
Redirect 301 /old-page.html https://example.com/new-page.html
# Redirect from www to non-www
RewriteEngine On
RewriteCond %{HTTP_HOST} ^www\.example\.com [NC]
RewriteRule ^(.*)$ https://example.com/$1 [L,R=301]
# Redirect from non-www to www
RewriteEngine On
RewriteCond %{HTTP_HOST} ^example\.com [NC]
RewriteRule ^(.*)$ https://www.example.com/$1 [L,R=301]
# Redirect an old URL pattern
RewriteEngine On
RewriteRule ^product/(.*)$ /shop/$1 [R=301,L]
# Redirect with parameters
RewriteEngine On
RewriteCond %{QUERY_STRING} ^id=(.*)$
RewriteRule ^product\.php$ /item/%1? [R=301,L]Managing DNS (Zone Editor)
Zone Editor lets you manage the DNS records of your domains.
Accessing Zone Editor
- Go to DOMAINS → Zone Editor
- Select the domain you want to edit
- Click Manage
Types of DNS record
A Record (Address Record)
Links a domain to an IPv4 address.
Example:
- Name:
example.com - Record: A
- Address:
192.0.2.1 - TTL: 14400
Use:
- Primary domain → server IP
- Subdomains → server IP
To create one:
- Click +A Record
- Enter the name (@ for the domain root, or the name of a subdomain)
- Enter the IP address
- Set the TTL (caching time)
- Click Add an A Record
AAAA Record (IPv6 Address)
Like an A record, but for IPv6.
Example:
- Name:
example.com - Record: AAAA
- Address:
2001:0db8:85a3::8a2e:0370:7334
CNAME Record (Canonical Name)
Creates an alias for another domain name.
Examples:
www.example.com→example.comblog.example.com→blogger.commail.example.com→mailserver.hosting.com
To create one:
- Click +CNAME Record
- Name: the name of the subdomain (for example,
www) - Record: the domain it points to (for example,
example.com) - Click Add a CNAME Record
MX Record (Mail Exchanger)
Specifies the mail servers for a domain.
Example:
- Name:
example.com - Priority: 0
- Destination:
mail.example.com
Priority:
- A lower number means a higher priority
- Usually 0, 10, 20 for different servers
To create one:
- Click +MX Record
- Enter the priority (usually 0 for the main server)
- Enter the mail server’s address
- Click Add an MX Record
TXT Record
Text information for a range of purposes.
Use:
- SPF records (spam protection)
- DKIM signatures (email authentication)
- DMARC policies
- Domain verification (Google, Microsoft and others)
- Site verification
Examples:
SPF:
v=spf1 +a +mx +ip4:192.0.2.1 ~allDKIM:
v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNA...DMARC:
v=DMARC1; p=quarantine; rua=mailto:dmarc@example.comGoogle verification:
google-site-verification=AbCd12345XyZ...To create one:
- Click +TXT Record
- Name: the name of the record (or @ for the root)
- Record: the text of the record
- Click Add a TXT Record
SRV Record (Service Record)
Defines the location of services.
Use:
- VoIP (SIP)
- Instant messaging (XMPP)
- Game servers
- Other specialised services
SIP example:
- Name:
_sip._tcp.example.com - Priority: 10
- Weight: 60
- Port: 5060
- Target:
sipserver.example.com
CAA Record (Certificate Authority Authorization)
Specifies which certificate authorities may issue SSL certificates for a domain.
Example:
- Name:
example.com - Flags: 0
- Tag: issue
- Value:
letsencrypt.org
To create one:
example.com CAA 0 issue "letsencrypt.org"
example.com CAA 0 issuewild "letsencrypt.org"
example.com CAA 0 iodef "mailto:admin@example.com"Editing DNS records
- Find the record in the list
- Click Edit
- Change the values
- Click Edit Record
Deleting DNS records
- Find the record
- Click Delete
- Confirm the deletion
Resetting the DNS zone
To restore the default settings:
- Zone Editor → Manage
- Click Reset Zone
- Confirm the action
This will restore:
- A records for the domain and www
- MX records for email
- The main service records
DNS propagation time
After you change DNS records:
- TTL: caching time (usually 4 hours = 14400 seconds)
- Full propagation: 24–48 hours
- Checking: use DNS lookup tools
Checking tools:
- WhatsMyDNS — propagation check
- MXToolbox — comprehensive DNS check
- DNS Checker — global check
# Check from the command line
nslookup example.com
dig example.com
host example.com
# Check a specific record type
dig example.com MX
dig example.com TXTDynamic DNS
Dynamic DNS updates the IP address in DNS when it changes (for dynamic IPs).
Usage
- Go to DOMAINS → Dynamic DNS
- Click Create
- Choose a domain or subdomain
- Click Create
- Copy the update URL you are given
- Set up your router, or use a DDNS client, to request this URL periodically
Checking your domain configuration
Domains Dashboard
The main Domains page shows:
- A list of all domains and subdomains
- The Document Root of each
- Management options (Manage, Delete)
- SSL status
Checking availability
After you add a domain:
- Wait for DNS to propagate (1–24 hours)
- Open the domain in a browser
- Check that:
- The site opens
- The right content is shown
- SSL works (if it is set up)
Troubleshooting
The domain doesn’t open:
- Check the DNS with Track DNS
- Make sure the A record points to the right IP
- Clear the DNS cache:
# Windows
ipconfig /flushdns
# macOS
sudo dscacheutil -flushcache
# Linux
sudo systemd-resolve --flush-cachesSomeone else’s site is shown:
- Check the Document Root in the domain’s settings
- Make sure the files have been uploaded to the right directory
SSL doesn’t work:
- Run AutoSSL for the domain
- Check SSL/TLS Status
Limits and quotas
Check your limits in the right-hand panel of cPanel:
| Item | Typical limit | Note |
|---|---|---|
| Addon Domains | 0–100 | Depends on your hosting plan |
| Subdomains | Unlimited/100 | Usually unrestricted |
| Parked Domains | 0–100 | Depends on your plan |
| Disk Space | Affects all domains | The account’s overall quota |
| Bandwidth | Affects all domains | Total traffic |
Moving domains
Moving a domain to your account
- Create an Addon Domain
- Upload the files to the domain’s Document Root
- Import the database (if there is one)
- Update the configuration (wp-config.php and so on)
- Change the DNS to the new name servers or an A record
Moving between accounts
To move a domain between cPanel accounts:
- Create a full backup of the domain
- Add the domain in the new account
- Restore the files and database
- Update the DNS
Best practice
- Plan the structure
- Use subdomains for logical separation
- Use addon domains for separate projects
- Document the purpose of each domain
- DNS management
- Keep a record of DNS changes
- Set sensible TTLs (4–24 hours)
- Use CAA records to protect SSL
- Redirects
- Use 301 for permanent changes
- Handle www and non-www consistently
- Always redirect to HTTPS
- Security
- Password-protect test subdomains
- Use SSL for all domains
- Check your DNS records regularly
- SEO
- Avoid duplicate content (aliases)
- Use 301 redirects properly
- Set up canonical URLs
Solving problems
Domain already exists
The domain has already been added on the server (possibly in another account).
Solution:
- Contact our support team
- It may need to be removed from the old account
DNS isn’t updating
Check:
- Your internet provider’s DNS cache
- Try a different DNS server (8.8.8.8, 1.1.1.1)
- Check with online tools
- Wait 24–48 hours
Addon Domain isn’t working
Common causes:
- The DNS doesn’t point to the server
- The Document Root is wrong
- The domain limit has been exceeded
- A problem with file permissions
Subdomains don’t open
Solutions:
- Check whether an A record has been created for the subdomain
- Make sure the files are in the right directory
- Clear your browser cache
- Check .htaccess for errors
Email doesn’t work after adding a domain
Check:
- The MX records are set up correctly
- Email accounts have been created for the domain
- Email Authentication (SPF, DKIM) is set up
See also
- SSL for addon domains
- Advanced DNS management
- Setting up email for domains
- Moving a site to a new domain
- SEO optimisation of domains
External links
Didn’t find the answer? Ask our support team — we’ll help.