Add and manage a domain in cPanel

Using the domain management in cPanel, you can connect additional domains to your web hosting and specify the directory from which their website is loaded. This is necessary, for example, if you want to run multiple websites within a single hosting account.

In this guide, we will show you step by step how to add a domain in the CURIAWEB cPanel, the correct document root or Document Root you define and subsequently check whether the domain has been set up correctly.

Important: Adding a domain in cPanel does not register a new domain and does not automatically change its DNS settings. The domain must also point to the correct hosting environment via DNS so that visitors can reach your website.

What happens when you add a domain in cPanel? #

By adding this, you are informing the web server that a specific domain is to be used within your hosting account.

Among other things, this specifies the directory from which the website for this domain is served.

This directory is used as Document Root or referred to as the document root.

Simplified:

example.com
        ↓
Document Root
        ↓
Website Files
        ↓
index.php / index.html / Application

When a visitor accesses the domain, the web server looks for the website in the directory configured for it.

Domain registration, DNS, and cPanel are different things #

When setting up a domain, you should distinguish between three areas:

Area	Task
Domain registration	The domain is registered and assigned to an owner.
DNS	Determines, among other things, which servers or services the domain points to.
cPanel	Configure the domain within the hosting account and assign a website directory to it, for example.

Briefly explained: A registered domain is not automatically connected to a website. DNS must point to the hosting, and the hosting account needs to know which website should be served for this domain.

When do you need to add an additional domain in cPanel? #

You need an additional domain, for example, if you want to run another independent website within the same hosting account alongside your existing main domain.

For example:

firma-a.ch
→ Website A

firma-b.ch
→ Website B

Both domains can be in the same hosting account, but use different website directories.

1. Log in to cPanel #

Log in to your CURIAWEB cPanel.

Then open:

Domains → Domains

Here you can see the domains currently assigned to your hosting account and add more domains.

2. Check existing domains #

Before adding a new domain, check the existing entries.

Check in particular whether the desired domain may have already been set up.

Practical Tip: If a domain already exists, you should not create a second similar entry on speculation. Check its existing configuration and document root first.

3. Create new domain #

In the domain management, select the function to create or add a new domain.

cPanel then opens the form for the new domain.

4. Enter domain name #

Enter the desired domain.

For example:

example.com

Enter only the domain name and not a full URL.

So use, for example:

example.com

and not:

https://example.com

Important: Protocol details like http:// or https:// do not belong in the domain name field.

5. Set Document Root #

When adding a domain, the Document Root especially important.

He determines in which directory the website files of this domain are located.

For example, a domain could be:

example.com

a directory like:

public_html/example/

to be assigned.

The actual directory structure depends on your hosting account and your desired configuration.

What does „Share document root“ mean? #

When creating a domain, cPanel can offer an option that allows the new domain to use the same document root as an already existing domain.

This would cause both domains to serve the same website files.

Simplified:

domain-a.ch ─┐
             ├── same Document Root
domain-b.ch ─┘
             ↓
        same files

If you for the new domain a standalone website want to operate, it must not accidentally use the same document root as another website.

Attention: Check this setting particularly carefully. If two domains use the same document root, they basically point to the same website file base.

Independent website with its own document root #

If each domain is to have its own website, the structure should be logically separated.

For example:

firma-a.ch
→ public_html/firma-a/

firma-b.ch
→ public_html/firma-b/

You can choose the actual directory names sensibly according to your environment.

Do not set the Document Root to public_html without careful consideration #

If a website already directly at:

public_html/

If you assign the same document root to an additional domain, both domains can use the same website files.

This may be intentional, but for a separate second website, it is usually not the desired result.

6. Create domain #

Check again before creating:

• the domain name
• the designated document root
• whether the domain should use its own or a shared document root

Then create the domain.

cPanel sets up the domain within the hosting account.

7. Check domain in the overview #

Return to the domain overview after creation.

The new domain should be displayed there.

Check the assigned Document Root in particular.

Important: The fact that the domain is displayed in cPanel does not automatically mean that it is already pointing to this hosting account on the internet. The DNS settings must also be correct for that.

8. Check Document Root in File Manager #

Open:

Files → File Manager

Then navigate to the document root of the newly set up domain.

For example, if you:

public_html/example/

have set as the Document Root, the website files for this domain should be located in this directory.

We explain how to work with the file manager in detail at Use cPanel File Manager.

Upload website files to the correct folder #

When setting up an existing website manually, upload its files to the document root of the domain in question.

For a PHP website, this could be a file, for example:

index.php

lie.

For example, with a static website:

index.html

be used as a startup file.

Common mistake: A domain can be set up correctly and still display the wrong website or no website at all if the files are in the wrong directory.

10. Check DNS connection #

To allow visitors to reach the domain, its DNS configuration must point to the correct hosting environment.

Which DNS records are required depends on how the domain and its DNS zone are managed.

If the DNS zone is managed via your cPanel, you can manage it via:

Domains → Zone Editor

view and edit.

We cover operation under Using the DNS Zone Editor in cPanel.

Domain exists in cPanel, but website is not reachable #

If the domain is set up in cPanel, but the expected website does not appear in the browser, check systematically:

• Is the domain name correct in cPanel?
• Does DNS point to the correct hosting environment?
• Is the correct document root configured?
• Are the website files in the correct directory?
• Is a suitable starting file or web application available?
• Was a DNS change made recently?

DNS changes are not always immediately visible everywhere #

After a DNS change, cached DNS information may still be used for a certain period of time.

As a result, the domain may temporarily resolve differently from different internet connections or devices.

That does not automatically mean that the cPanel domain configuration is faulty.

Check HTTPS and SSL #

Once the domain correctly points to the hosting account, it should also be accessible via HTTPS.

Call the domain, for example, via:

https://example.com

on.

When the browser displays a certificate warning, you should not simply assume that there is a problem with the website files.

DNS, domain configuration, and SSL certificate are different components of the setup.

SSL certificate can only become relevant after correct domain resolution #

For automated certificate provisioning, the domain normally needs to resolve correctly to the intended hosting environment or allow the required validation.

If the domain still points to an old server, certificate provision or validation may also be affected for this reason.

Domain shows the wrong website #

If a new domain suddenly displays another website of your hosting account, you should check the document root first.

Both domains may be using the same directory.

For example:

domain-a.ch
→ public_html/

domain-b.ch
→ public_html/

In this case, both domains access the same file base.

Domain shows a blank page or directory content #

If the document root is correct, but there is no matching website or start file in it, the domain cannot display the expected website.

Check in the file manager which files are actually in the assigned directory.

Domain shows a cPanel or default page #

If a standard or placeholder page appears instead of your website, you should also check:

• DNS resolution
• Domain assignment
• Document Root
• existing website files

A placeholder page does not automatically mean that your actual website has been deleted.

www and domain without www #

The variants:

example.com

and

www.example.com

are technically different hostnames.

A website can be configured so that both variants work and one of them redirects to the preferred variant.

Which variant is used as the main address should be defined consistently within the website.

not to be confused with an additional, standalone website #

The wwwA variant of a domain is usually not treated as a completely independent second website.

It usually belongs to the same website as the domain without www.

Multiple domains for the same website #

It is technically possible to connect multiple domains to the same website content.

However, that does not mean it makes sense to make the same website permanently accessible under multiple different domains without redirection.

If an additional domain is merely supposed to lead to the actual main domain, a redirect is often the cleaner solution.

We explain how to set up such a redirection at Set up domain redirection in cPanel.

Redirection and a shared document root are not the same #

These two variants differ technically:

Shared document root:
domain-a.ch → same website files
domain-b.ch → same website files

Redirect:
domain-b.ch → browser is redirected to domain-a.ch

With a redirect, the address in the browser changes. With a shared document root, this does not have to be the case.

Subdomain or additional domain? #

A subdomain is a subordinate hostname of an existing domain.

For example:

shop.example.com

An additional independent domain, on the other hand, would be:

example-shop.com

We explain how to set up a subdomain in the next article at Create subdomain in cPanel.

Check Document Root subsequently #

If you later don't know which directory belongs to a domain, open:

Domains → Domains

There you can check the domain mapping.

When dealing with multiple websites, do not rely solely on the folder names in the file manager.

Do not change the document root on suspicion #

If a production website is working, you should not change its document root without a specific reason.

A change can cause the web server to suddenly serve files from a different directory.

This does not automatically move the actual website files to the new directory.

Attention: Changing the document root is not a file move. If you change the mapping, the existing files generally remain in their previous location.

Removing a domain – what happens to the website files? #

When you remove a domain from cPanel domain management, you should not assume that this automatically deletes all associated website files, databases, or email data.

The domain configuration and the stored content are different components of the hosting account.

Therefore, always check which resources belong to the domain and whether they are still needed before removing them.

Do not delete the domain to fix a DNS issue #

If a domain suddenly becomes unreachable, removing and re-adding it in cPanel is usually not the first sensible step.

Check first:

• DNS resolution
• Document Root
• Website files
• SSL
• potential error message

Unnecessary deletion of the domain configuration can cause additional problems.

Point domain to another folder #

If a domain is to use a different website in the future, its mapping to the corresponding document root must be adjusted correctly.

Check beforehand where the new website is hosted and whether the previous website is still needed.

Create a backup of the existing files and, if necessary, the database in case of major changes.

Domain and database are not automatically linked to each other #

A domain does not automatically possess a specific MySQL database.

A database-based application connects to the intended database using its own configuration data.

In WordPress, this information can be found in, for example:

wp-config.php

This means:

Domain
→ Document Root
→ WordPress files
→ wp-config.php
→ Database connection

If you only change the domain or the document root, this does not automatically move or adjust a database.

Consider domain and email separately as well #

The website and email delivery of a domain are also technically different services.

Therefore, a change to the website association does not automatically mean that the email delivery should also change.

Especially when making DNS changes, you should be careful not to unintentionally modify existing mail settings.

Use domain from external registrar #

A domain does not necessarily have to be registered with the same provider as the web hosting.

If an externally registered domain is to be connected to your hosting, it must be set up in cPanel and its DNS configuration appropriately aligned with the hosting environment.

The registration itself remains with the respective domain provider.

A change of nameservers is not always strictly necessary #

A domain can in principle also point to web hosting with externally managed DNS.

Whether the nameservers are changed or individual DNS records are adjusted depends on the existing DNS configuration and the desired setup.

Do not change nameservers on a whim, especially if email or other services are already running via the domain.

Attention: A name server change affects the entire DNS zone. Existing records for the website, email, and other services must be taken into account.

Domain only works on some devices #

If a domain shows the new website on one device shortly after a DNS change and still the old website on another, cached DNS data can be the cause.

Therefore, do not check the cPanel configuration again immediately if the change was made only recently.

Domain still points to old server after migration #

If the website files are already on the new hosting, but the domain still reaches the old server, you should check the DNS configuration.

Moving files or adding a domain in cPanel does not automatically change the public DNS resolution.

Error 404 after adding a domain #

When the domain basically reaches the correct server, but an error 404 displayed, the following can be checked, among other things:

• correct document root
• existing startup file or application
• Path of the requested page
• Redirection or rewrite rules

A 404-Error does not automatically mean that the domain itself was set up incorrectly.

Error 403 after adding a domain #

An error 403 Forbidden can be related, for example, to file permissions, directory access, security rules, or the existing website structure.

We will cover systematic error analysis later under Fix 403 Forbidden.

Error 500 after adding a website #

If the domain reaches the correct document root, but the application there 500 Internal Server Error causes, the problem is often not the domain mapping itself.

Possible causes can be PHP errors or faulty configurations, for example.

We are treating the diagnosis under Fixing a 500 Internal Server Error.

Remove domain #

If a domain is no longer to be used in this hosting account, you can remove it via:

Domains → Domains

manage or remove.

Check carefully beforehand:

• whether the domain still uses an active website
• which document root is assigned
• whether files are still needed
• whether a database belongs to the website
• whether email services could be affected
• whether a fuse is required

Important: Removing a domain from cPanel and canceling a domain registration are two completely different processes.

Recommended procedure for adding a new domain #

1. Check if the domain is registered and intended for use.
2. Log in to cPanel.
3. Open Domains → Domains.
4. Select the function to create a new domain.
5. Enter the domain name without https:// one.
6. Decide whether the domain requires its own document root.
7. Check the proposed document root.
8. Create the domain.
9. Check the domain in the overview.
10. Check the assigned directory in the file manager.
11. Place or transfer the website files into the correct document root.
12. Check the DNS configuration.
13. Test the domain in the browser.
14. Then check HTTPS and the most important website functions.

Recommended check if the domain shows the wrong website #

1. Check domain name in cPanel.
2. Check document root.
3. Check files in document root.
4. Check DNS resolution.
5. Check whether multiple domains use the same document root.
6. Check redirects.
7. Only make changes to the domain configuration after that.

Basic rule: If a website is displayed incorrectly, do not immediately move files or delete domains. First, determine which server and which document root the domain is actually using.

When should you contact support? #

If a domain does not display the expected website despite correct setup, you should document the current state as precisely as possible.

For an analysis, the following information is particularly helpful:

• affected domain
• whether the domain was newly added or has been in use for a longer time
• document root displayed in cPanel
• whether the website files are present there
• whether DNS was recently changed
• which page or error message appears in the browser
• whether HTTP and HTTPS react differently
• whether the domain was previously used on another server

Do not transmit any passwords or other confidential access credentials.

Summary #

You set up an additional domain in the CURIAWEB cPanel under Domains → Domains a. Enter the domain name without http:// or https:// and check the intended one particularly carefully Document Root.

If the domain is to have an independent website, it should not accidentally use the same document root as another website. The website files must then be located in the assigned directory.

Adding the domain in cPanel does not automatically change its public DNS configuration. For the domain to be accessible, the DNS must also point to the correct hosting environment.

Therefore, if a domain displays the wrong website, you should first check the domain mapping, document root, website files, and DNS. Do not remove the domain on suspicion and do not move any files before the actual cause has been determined.