How to Manage DNS Records Using cPanel Zone Editor
DNS (Domain Name System) controls how your domain connects to websites, email services, and other online applications.
Whether you're connecting a domain to your hosting account, setting up business email, or verifying ownership of a domain, you may need to add or modify DNS records.
Lagrange Point Media (LPM) provides DNS management tools through cPanel for domains whose DNS zones are managed by the hosting server.
This guide explains how to use cPanel Zone Editor, understand common DNS record types, and avoid configuration mistakes that could interrupt your website or email service.
1. Understanding DNS Records
DNS records are instructions that tell computers and online services how to handle requests associated with your domain.
Different record types serve different purposes.
For example:
-
A records connect hostnames to IPv4 addresses.
-
AAAA records connect hostnames to IPv6 addresses.
-
CNAME records create aliases between hostnames.
-
MX records identify mail servers.
-
TXT records store text-based information, including email authentication and domain verification data.
-
SRV records identify certain network services.
A domain may contain many DNS records working together.
Important: Changing one record can affect your website, email, or another connected service. Always identify what a record does before modifying it.
2. Accessing cPanel Zone Editor
To open Zone Editor:
-
Sign in to the LPM Client Portal.
-
Navigate to Services > My Services.
-
Select your active hosting service.
-
Open cPanel.
-
Search for Zone Editor.
-
Click the Zone Editor icon.
You'll see a list of domains with DNS zones available to your hosting account.
Locate the domain you want to manage and click Manage.
Note: The exact options displayed may vary depending on your cPanel configuration and the record types supported by your hosting environment.
3. Make Sure You're Editing DNS in the Correct Place
Before changing records, determine which provider currently manages your domain's authoritative DNS.
Your domain may use:
-
Nameservers associated with LPM hosting.
-
Your domain registrar's nameservers.
-
Cloudflare or another DNS provider.
-
A third-party website or email platform's DNS service.
If your domain uses external nameservers, changes made in cPanel Zone Editor may not affect the DNS records visitors and email providers actually receive.
For example, if your domain uses Cloudflare nameservers, its public DNS records are generally managed through Cloudflare rather than cPanel.
Important: Having a domain listed in cPanel does not automatically mean cPanel controls its public DNS.
4. Understanding A Records
An A record connects a hostname to an IPv4 address.
A records are commonly used to point websites and subdomains to hosting servers.
Example:
Type: A
Name: yourbusiness.com
Value: 192.0.2.10
The IP address above is for illustration only.
To add an A record:
-
Open Zone Editor.
-
Click Manage beside your domain.
-
Click Add Record or select the option to add an A record.
-
Enter the hostname.
-
Enter the correct IPv4 address.
-
Review the TTL setting.
-
Save the record.
Important: Use the actual IP address provided for your hosting service. An incorrect address can send visitors to the wrong server.
5. Understanding AAAA Records
An AAAA record connects a hostname to an IPv6 address.
It serves a similar purpose to an A record but uses IPv6 rather than IPv4.
Not every hosting service or website configuration requires an AAAA record.
Warning: Do not create an AAAA record unless the destination server is configured to serve your website over that IPv6 address.
An incorrect AAAA record can cause connection problems for visitors whose devices prefer IPv6.
6. Understanding CNAME Records
A CNAME record creates an alias from one hostname to another hostname.
For example:
Type: CNAME
Name: www.yourbusiness.com
Value: yourbusiness.com
This tells DNS resolvers that the www hostname is an alias of the root domain.
CNAME records are also commonly used for:
-
Third-party website services.
-
Email service configuration.
-
Domain verification.
-
Application integrations.
-
Custom service hostnames.
To create a CNAME record:
-
Open Zone Editor.
-
Select your domain.
-
Add a new CNAME record.
-
Enter the hostname.
-
Enter the destination hostname.
-
Save the record.
Important: A CNAME record must point to a hostname, not an IP address.
A hostname with a CNAME record generally cannot also have other DNS record types at that same name.
7. Understanding MX Records
MX (Mail Exchange) records identify the mail servers responsible for receiving email for your domain.
For example, if you use Microsoft 365 or Google Workspace, your MX records normally point to mail servers operated by that provider.
An MX record includes:
-
A destination mail server.
-
A priority value.
Lower numerical priority values are generally preferred over higher ones.
To modify MX records:
-
Open Zone Editor.
-
Select your domain.
-
Filter the record list to display MX records.
-
Review the existing entries.
-
Add, edit, or remove records as required by your email provider.
-
Save the changes.
Warning: Incorrect MX records can prevent your domain from receiving email.
Before replacing existing MX records, confirm the exact values required by your email service.
8. Understanding TXT Records
TXT records store text-based information associated with a domain.
They are frequently used for:
-
SPF email authentication.
-
DKIM email authentication.
-
DMARC policies.
-
Domain ownership verification.
-
Third-party application verification.
For example, a service may ask you to add a TXT record containing a verification code.
To add a TXT record:
-
Open Zone Editor.
-
Select your domain.
-
Click Add Record.
-
Choose TXT.
-
Enter the requested hostname.
-
Paste the exact TXT value supplied by the service.
-
Save the record.
Tip: Copy verification values exactly. Missing characters, extra spaces, or incorrect hostnames can cause verification to fail.
9. Understanding SPF Records
SPF (Sender Policy Framework) helps receiving mail servers determine which systems are authorized to send email using your domain.
SPF policies are published using TXT records.
An example SPF record might look like:
v=spf1 include:example.com -all
This is an illustration, not a configuration you should copy.
Your SPF record must reflect the services that actually send email for your domain.
These might include:
-
Your hosting server.
-
Microsoft 365.
-
Google Workspace.
-
A transactional email provider.
-
An email marketing platform.
Important: A domain should not publish multiple separate SPF policy records at the same hostname.
If you use multiple sending services, their authorized sending mechanisms generally need to be combined into one valid SPF policy.
Incorrect SPF configuration can cause legitimate messages to fail authentication.
10. Understanding DKIM Records
DKIM (DomainKeys Identified Mail) uses cryptographic signatures to help receiving servers verify that email was authorized by the signing domain and has not been modified in transit.
DKIM records are published in DNS, typically as TXT records, although some providers use CNAME records for their setup.
The record name often contains a selector followed by:
._domainkey
For example:
selector1._domainkey.yourbusiness.com
The exact record name and value depend on your email provider.
Important: Do not generate random DKIM records or copy another domain's values. Use the records supplied by the system responsible for signing your outgoing email.
11. Understanding DMARC Records
DMARC (Domain-based Message Authentication, Reporting, and Conformance) builds on SPF and DKIM.
It allows a domain owner to publish a policy describing how receiving servers should handle messages that fail DMARC authentication.
A DMARC record is published as a TXT record at:
_dmarc.yourbusiness.com
An example monitoring policy is:
v=DMARC1; p=none
This example requests no enforcement action and is not a complete security strategy.
DMARC policies commonly include:
p=none
Requests monitoring without a DMARC-specific rejection or quarantine policy.
p=quarantine
Requests that failing messages be treated as suspicious.
p=reject
Requests that failing messages be rejected.
Warning: Enforcing a restrictive DMARC policy before properly configuring SPF or DKIM alignment can interfere with legitimate email delivery.
12. Adding a New DNS Record
The general process for adding a DNS record in cPanel is:
-
Open Zone Editor.
-
Click Manage for the appropriate domain.
-
Select Add Record.
-
Choose the required record type.
-
Enter the hostname.
-
Enter the destination or record value.
-
Review the TTL setting.
-
Save the record.
After saving, confirm that the record appears in the DNS zone.
Important: Some DNS providers automatically append your domain name to the hostname you enter. Review the completed record to avoid accidentally duplicating the domain name.
13. Editing an Existing DNS Record
To edit a record:
-
Open Zone Editor.
-
Select your domain.
-
Locate the record.
-
Click Edit.
-
Modify the required information.
-
Save the changes.
Before editing, record the original values so you can restore them if necessary.
Tip: If you're replacing a website's A record, confirm that you're editing the correct hostname. Your root domain and www hostname may use different records.
14. Deleting DNS Records
Removing a DNS record can disconnect a service that depends on it.
To delete a record:
-
Open Zone Editor.
-
Select your domain.
-
Locate the record.
-
Click Delete.
-
Confirm the deletion.
Warning: Do not delete unfamiliar records simply because you don't recognize them.
Some records are used for email verification, security, automatic service discovery, or third-party integrations.
If you're uncertain about a record's purpose, investigate it before removing it.
15. Understanding DNS TTL
TTL stands for Time to Live.
It tells DNS resolvers how long they may cache a record before checking for updated information.
TTL values are commonly expressed in seconds.
For example:
300 seconds: 5 minutes
3600 seconds: 1 hour
14400 seconds: 4 hours
A lower TTL can reduce the time some resolvers retain an old record after a change.
However, lowering TTL does not instantly clear information that has already been cached.
Tip: Before a planned DNS migration, reducing the TTL in advance may help limit the duration of cached old records.
16. How Long Do DNS Changes Take?
DNS changes may become visible quickly, but some networks can continue using cached information.
The timing depends on:
-
The previous TTL value.
-
Resolver caching behavior.
-
The DNS provider.
-
The type of change.
-
Nameserver delegation updates.
Some changes appear within minutes, while others can take hours.
Nameserver changes may take longer to become consistently visible across networks.
Important: DNS propagation does not mean every server on the internet updates at the same moment.
17. Checking Your DNS Records
You can use a public DNS lookup tool to check what records are being returned.
For example:
To check a record:
-
Open the DNS lookup tool.
-
Enter your domain name.
-
Select the record type you want to check.
-
Run the lookup.
-
Compare the result with your intended configuration.
Common record types to check include:
-
A
-
AAAA
-
CNAME
-
MX
-
TXT
-
NS
Important: A public DNS lookup shows information returned by the queried DNS system. It does not necessarily prove that every network is receiving the same result.
18. Common DNS Problems
My Website Doesn't Load After Changing an A Record
The IP address may be incorrect, the hosting account may not recognize the domain, or the server may not be configured to serve the website.
My DNS Changes Aren't Appearing
You may be editing DNS at a provider that isn't authoritative for your domain.
My Email Stopped Working
The MX records may have been changed, deleted, or replaced.
My Domain Verification Keeps Failing
The verification TXT or CNAME record may have the wrong hostname or value, or the service may not yet detect the change.
My WWW Address Doesn't Work
The www hostname may not have a valid DNS record.
My SPF Record Is Invalid
You may have multiple SPF policies, incorrect syntax, or an unsupported configuration.
My Website Works for Some People but Not Others
Different DNS resolvers may still have cached information, or different address records may lead to inconsistent destinations.
19. DNS Management and External Email Providers
You can use LPM for website hosting while keeping your email with another provider.
For example:
-
Website hosting through LPM.
-
Email through Microsoft 365.
-
Domain registration through another company.
In this arrangement, your DNS records must be configured to support all three services.
If you change nameservers, you must ensure that the new authoritative DNS provider contains the necessary records.
Warning: Do not replace email-related DNS records with hosting defaults unless you intend to change your email service.
20. Getting Help from LPM
If you need help identifying the correct DNS records or troubleshooting a domain connection, contact LPM support.
Submit a support ticket through the LPM Client Portal.
Please include:
-
Your domain name.
-
Your DNS provider, if known.
-
The record type you're trying to configure.
-
The service you're connecting.
-
Any error messages or verification failures.
-
Whether you recently changed nameservers.
Do not include passwords or sensitive account credentials in your support ticket.
LPM can assist with hosting-related DNS configuration. Some external services may require you to obtain their exact DNS settings directly from the service provider.
Additional Resources: