Introduction #
In this doc we’ll explain how to manage your domain(s) and DNS records/zones in cPanel. After reading this doc, you’ll know how to use the domains page, how to use and edit DNS records/zones, and more.
Domains Page #
The Domains page in cPanel is the main place where you can view the domains and subdomains connected to your hosting account. It shows how each domain is linked within the hosting environment and which document root is assigned to it.
At ProRedLine, this page is mainly used to review the domains already connected to your Web Hosting or Site Hosting service and to manage certain domain-related settings that are available within cPanel.
What the Domains Page Is Used For #
The Domains page gives an overview of the domains associated with your hosting account. From this page, you can view the primary domain, any connected additional domains where applicable, and any subdomains that exist under the account.
It also shows the document root linked to each domain, which is important for understanding where that domain loads its website files from.
In practical terms, this page helps you see how domains are connected to website directories and how they are organised within the hosting account.
Where to Find It #
To open the Domains page in cPanel:
- log in to cPanel
- go to the Domains section
- click Domains
From there, you will see the domains currently associated with your account.
What You May See on This Page #
On the Domains page, you will typically see:
- the primary domain of the hosting account
- any connected additional domains, where applicable
- any subdomains that exist under the account
- the document root assigned to each domain
This makes it easier to understand which folder each domain or subdomain points to.
Adding Domains and Subdomains #
Subdomains can generally be created from the Domains page by using the Create A New Domain option. During that process, you will normally be asked to define the document root that the subdomain should use.
At ProRedLine, addon and parked domains are handled by ProRedLine rather than being added directly by the customer through this page. This helps ensure the setup is applied correctly and stays consistent with the hosting service and package limits.
Force HTTPS Redirect #
The Domains page may also include a Force HTTPS Redirect option for domains and subdomains. This setting is off by default, but enabling it is generally recommended once the domain is correctly secured with SSL.
When enabled, visitors who try to access the website through http:// are automatically redirected to the secure https:// version of the same address. This helps ensure that traffic uses the secure version of the site instead of the unsecured one.
DNS Zone Editor #
The DNS Zone Editor in cPanel is the area where you manage the DNS records for your domain. These records control how the domain connects to websites, email services, and external platforms.
At ProRedLine, access to the DNS Zone Editor is included so customers can manage the DNS records needed for normal domain use, website routing, email delivery, and service verification.
What the DNS Zone Editor Is Used For #
The DNS Zone Editor is used when you need to control how a domain behaves at DNS level. This can include pointing a domain to a website, configuring email-related records, verifying a domain for external services, or connecting the domain to third-party platforms.
Because DNS changes affect how services are reached, updates made here do not always apply instantly. After editing a record, time is still needed for DNS propagation.
Where to Find It #
To open the DNS Zone Editor in cPanel:
- log in to cPanel
- go to the Domains section
- click Zone Editor
From there, you can view and manage the DNS records linked to your domain.
Which Record Types Can Be Managed #
The DNS Zone Editor can be used to manage common record types such as A, AAAA, CNAME, TXT, and MX. Depending on the setup, more advanced record types such as SRV and CAA may also be available.
These records are used for different purposes, such as website routing, email delivery, authentication, verification, and service integration.
Nameservers and Glue Records #
The DNS Zone Editor is intended for record-level management, not for changing the nameserver setup of the domain itself.
At ProRedLine, nameserver changes and glue record management are not part of the normal customer-facing DNS Zone Editor workflow. Custom nameserver setups are also not provided as a standard service.
In limited and justified cases, nameserver-related changes may be reviewed manually through support.
Why This Is Restricted #
Restricting nameserver-level changes helps reduce the risk of domain misconfiguration, protects DNS integrity, and lowers the chance of avoidable outages caused by incorrect delegation settings.
For most normal use cases, direct DNS record management through the Zone Editor is sufficient and does not require custom nameserver changes.
Redirects #
Redirects allow you to forward visitors from one URL to another.
This is commonly used when a website moves, a page is renamed, or traffic should be sent to a different location.
Redirects configured in cPanel work on the server level and take effect immediately.
What Redirects Are Used For #
Redirects are commonly used to:
- Forward an old domain to a new domain
- Redirect one page to another page
- Force visitors to use a specific URL
- Prevent access to outdated pages
Redirects help avoid broken links and visitor confusion.
Where to Find Redirects in cPanel #
- Log in to cPanel
- Go to the Domains section
- Click Redirects
This opens the Redirects management interface.
Types of Redirects #
Permanent Redirect (301) #
- Used when a URL has permanently changed
- Search engines update their records
- Recommended for most website changes
Temporary Redirect (302) #
- Used when a redirect is temporary
- Search engines do not update indexing
- Less commonly used
If you are unsure, use a 301 redirect.
Setting Up a Redirect #
To create a redirect:
- Select the redirect type (301 or 302)
- Choose the domain to redirect from
- Enter the source path
- Enter the destination URL
- Save the redirect
Redirects apply immediately after saving.
Redirecting a Full Domain #
To redirect an entire domain:
- Leave the source path empty
- Enter the destination domain
Example:
example.com→newexample.com
Redirecting a Single Page #
To redirect a specific page:
- Enter the page path only
Example:
/old-page.html→/new-page.html
Still need help after reading this article?
