cPanel Subdomain Setup: 10 Common Questions Answered

What is the difference between a subdomain and an addon domain in cPanel?

A subdomain is a prefix attached to your existing domain (store.example.com is a subdomain of example.com). It shares the parent domain's DNS zone and hosting account resources.

An addon domain is a completely separate domain name (example.net) that you host in the same cPanel account as your main domain. It gets its own DNS zone, its own document root, and can have its own subdomains.

You use a subdomain when you want to organize content under your existing brand. Use an addon domain when you are hosting a second website with a different name. In support tickets I handled, customers often tried to create subdomains for entirely separate business projects when they actually needed addon domains.

How do I create a subdomain in cPanel?

Log into cPanel and find the Domains section. Click Subdomains. Enter the subdomain prefix in the first field (for example, 'blog' to create blog.example.com).

Select the parent domain from the dropdown if you have multiple domains in the account. cPanel will auto-populate the document root field with public_html/subdomain_name. You can change this path if you want the files in a different directory.

Click Create. cPanel immediately adds the DNS A record and creates the document root folder. You will see a success message with the full subdomain name and the document root path. Write down that path; you need it for FTP uploads and file manager navigation.

• The subdomain appears in the Subdomains table where you can later modify the document root or remove it.
• If the Create button is grayed out, check that you have not hit your account's subdomain limit in the hosting plan.
• Parent domain DNS must already point to the cPanel server. You cannot create subdomains for domains still using external parking nameservers.

Why can't I access my subdomain right after creating it?

The subdomain is live on the server the moment you click Create. The problem is DNS caching on your computer or network.

Your operating system and browser cache DNS lookups for speed. When you create a subdomain, your computer still has a cached 'domain not found' response from before the subdomain existed. Flush the DNS cache on your machine. On Windows, open Command Prompt and run 'ipconfig /flushdns'. On macOS, run 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder' in Terminal. On Linux, restart the systemd-resolved service or nscd if installed.

Test in a private browsing window or from your phone on mobile data to bypass local cache. If the subdomain works there but not on your main browser, it is definitely a cache issue. ISP-level DNS caching can add another 10-30 minutes of delay, but that is rare with modern recursive resolvers.

Does my existing SSL certificate cover the new subdomain?

Not automatically. Standard SSL certificates are issued for specific hostnames. A certificate for example.com does not cover blog.example.com.

If you have a wildcard certificate (*.example.com), it covers all first-level subdomains like blog.example.com and shop.example.com, but not nested subdomains like api.blog.example.com. Check your certificate details in cPanel under SSL/TLS Status to see what hostnames are included.

AutoSSL in cPanel can automatically issue free Let's Encrypt certificates for subdomains if enabled on your server. After you create the subdomain, AutoSSL will attempt to provision a certificate on its next run, usually within a few hours. You can trigger an immediate AutoSSL run for the subdomain from the SSL/TLS Status interface.

If AutoSSL is not available, manually install a certificate for the subdomain through the SSL/TLS > Manage SSL Sites interface. You will need to generate a CSR for the subdomain or use a service like Let's Encrypt via the cPanel interface.

Can I point a subdomain to a different server or IP address?

Yes, but you edit DNS records rather than the cPanel subdomain settings. Go to Zone Editor in cPanel, find the A record for the subdomain, and change the IP address to the external server's IP.

If you want the subdomain to point elsewhere, you may not need to create it as a cPanel subdomain at all. Just add the DNS record manually. A cPanel subdomain creation is only necessary when you want to host the content on the same server in a specific document root.

After changing the A record, propagation takes the usual 5 minutes to 48 hours depending on TTL and caching. The subdomain will no longer serve files from the cPanel document root once the new IP propagates.

What is the document root and why does it matter?

The document root is the directory on the server where the subdomain's files are stored. When someone visits blog.example.com, the web server looks in that directory for index.html, index.php, or whatever default document is configured.

cPanel defaults to public_html/subdomain_name, so a subdomain called 'blog' would serve files from /home/username/public_html/blog. You can override this during creation or change it later in the Subdomains interface.

Picking the right document root matters for organization and security. Keep subdomain files in separate directories so a compromised script in one subdomain cannot easily access files in another. I have seen incidents where all subdomains shared the same public_html root, and a vulnerability in a test subdomain gave an attacker access to the production site files.

• Nested paths are allowed; you can set the document root to public_html/projects/blog if you want deeper organization.
• Changing the document root after creation does not move files. You will need to manually move or copy files to the new path via FTP or File Manager.
• Make sure the document root path has correct ownership (your cPanel username) and permissions (755 for directories, 644 for files). Incorrect ownership breaks PHP execution and file uploads.

How do I delete or remove a subdomain?

Go to the Subdomains interface in cPanel. Find the subdomain in the list and click Remove or the trash icon. cPanel will ask for confirmation.

Deleting the subdomain removes the DNS A record from the zone file and unlinks the document root, but it does not delete the files in the document root directory. If you want to free up disk space, manually delete the folder via File Manager or FTP after removing the subdomain.

Email accounts tied to the subdomain (like [email protected]) are not automatically deleted. Remove those separately under Email Accounts if you no longer need them. DNS propagation for the removal is usually faster than creation because caches respect shorter TTLs for negative responses.

Can I create email accounts for a subdomain?

Yes. Go to Email Accounts in cPanel and create an account using the subdomain in the domain dropdown (for example, [email protected]). The subdomain must exist in cPanel first.

Email routing for subdomains works identically to the main domain. MX records are inherited from the parent domain unless you override them in the Zone Editor. Most users do not need separate MX records for subdomains unless the subdomain email is handled by a different mail server.

Remember that creating the subdomain itself does not set up email. The Subdomains interface only handles web hosting and DNS A records. Email configuration is always a separate step in the Email section of cPanel.

What are the most common subdomain setup mistakes?

First mistake: trying to create a subdomain for a domain that is not yet added to cPanel or still pointing to external nameservers. The parent domain must be fully configured in the cPanel account with DNS managed by the server.

Second mistake: not flushing local DNS cache after creating the subdomain, then opening a support ticket claiming the subdomain does not work. Test from multiple devices or networks before escalating.

Third mistake: assuming the SSL certificate automatically covers subdomains. You must explicitly request or configure subdomain SSL coverage through a wildcard certificate or individual certificates.

Fourth mistake: uploading files to the wrong directory. If you created a subdomain with the default document root public_html/blog but uploaded files to public_html, the subdomain will show an empty directory listing or cPanel's default page. Always verify the document root path in the Subdomains table before uploading.

Quick reference table

Here is a summary of the key subdomain setup parameters and their defaults:

• Document root: public_html/subdomain_name (customizable during creation or later)
• DNS A record: Automatically created pointing to server IP; propagation 5 mins to 48 hours
• SSL certificate: Not included; requires separate issuance via AutoSSL, Let's Encrypt, or manual install
• Email accounts: Not created automatically; set up separately in Email Accounts using the subdomain
• Deletion: Removes DNS record and unlinks document root; does not delete files or email accounts
• Subdomain limits: Check your hosting plan; shared hosting typically allows 100-unlimited, reseller plans vary per package