Hosting & VPS Guides

Managing DNS Zones in cPanel and Plesk

Practical guide to editing DNS zones in cPanel and Plesk: A, CNAME, MX, TXT, SPF, DKIM, DMARC, TTL, nameservers and safe DNS changes.

By CheckDomainHealth Editorial Team Reviewed by Dionis Ceban Updated Jun 28, 2026 9 min read Beginner

Introduction

A DNS zone is the set of records that tells the internet where your website, email and domain services should go. In hosting panels like cPanel and Plesk, DNS zones are usually managed through tools such as Zone Editor, DNS Zone Manager or DNS Settings.

Editing DNS records is powerful, but mistakes can break websites, email, SSL validation, verification records or subdomains. Before changing records, you should know which DNS provider is authoritative, what each record does and how to verify the result after saving changes.

Quick answer

Quick answer

Use cPanel or Plesk DNS tools to manage records only if that server is authoritative for the domain. Edit A and CNAME records for websites, MX records for email routing, TXT records for SPF/verification, DKIM records for email signing, and DMARC records for policy/reporting. Back up the zone before changes and verify records with DNS Lookup after saving.

DNS zones

Managing DNS zones in cPanel or Plesk means adding, editing or deleting DNS records for a domain.

A DNS zone may include records for:

  • website routing
  • www subdomain
  • mail routing
  • SPF authentication
  • DKIM authentication
  • DMARC policy
  • SSL validation
  • domain ownership verification
  • subdomains
  • FTP or control panel hostnames
  • CDN setup
  • third-party services

The most important question is whether cPanel or Plesk is the active DNS provider. If your domain uses external nameservers, changes made inside cPanel or Plesk may not affect public DNS.

Authoritative nameservers

Before editing DNS in cPanel or Plesk, confirm where DNS is actually hosted.

DNS may be managed by:

  • cPanel server
  • Plesk server
  • domain registrar
  • Cloudflare
  • hosting provider DNS
  • external DNS provider
  • Microsoft 365 or Google verification zone
  • CDN provider

If your domain nameservers point to Cloudflare, editing DNS inside cPanel may not change the public records. You must edit records where the authoritative nameservers are managed.

Verify DNS zone changes

Use DNS Lookup to confirm authoritative nameservers, A, CNAME, MX, TXT and other records after editing in cPanel or Plesk.

Run DNS Lookup →

cPanel DNS

In cPanel, DNS records are usually managed in Zone Editor.

Common cPanel path:

  • Domains → Zone Editor → Manage

Typical actions:

  • add A record
  • add CNAME record
  • add MX record
  • add TXT record
  • edit existing record
  • delete unused record
  • manage email routing
  • view DNSSEC if supported
  • configure DKIM/SPF in Email Deliverability

Some cPanel servers separate DNS records and email routing settings. Changing MX records may also require checking Email Routing: Local, Remote or Automatic.

Plesk DNS

In Plesk, DNS records are usually managed through DNS Settings for the domain.

Common Plesk path:

  • Websites & Domains → domain → DNS Settings

Typical actions:

  • add record
  • edit record
  • remove record
  • switch DNS service on/off
  • reset zone to default
  • manage SOA settings
  • manage mail-related records
  • apply DNS template

If Plesk DNS service is disabled for the domain, public DNS may be managed elsewhere.

Record types

A record

Points a hostname to an IPv4 address.

AAAA record

Points a hostname to an IPv6 address.

CNAME record

Points one hostname to another hostname.

MX record

Routes incoming email to mail servers.

TXT record

Stores text values for SPF, verification and security records.

DKIM record

Publishes email signing key for a selector.

DMARC record

Publishes email authentication policy at _dmarc.

CAA record

Controls which certificate authorities may issue SSL certificates.

SRV record

Defines service location for some protocols.

SOA record

Contains zone authority and timing information.

NS record

Defines nameservers for the domain or delegated subdomain.

Website records

Website routing usually depends on A, AAAA and CNAME records.

Common setup:

  • example.com → A record to hosting IP
  • www.example.com → CNAME to example.com
  • staging.example.com → A or CNAME to staging server
  • cdn.example.com → CNAME to CDN hostname

When moving only the website to a new host, usually update A/AAAA/CNAME records. Do not change MX records unless email is also moving.

Email records

Email depends on MX records and authentication records.

Important email DNS records:

  • MX for incoming mail routing
  • SPF TXT for authorized sending sources
  • DKIM TXT/CNAME for signed outgoing mail
  • DMARC TXT for policy and reports
  • autodiscover CNAME for email client setup
  • mail A/CNAME record if used
  • reverse DNS for the sending IP if running a mail server

Email records are often lost during nameserver or hosting migrations. Always copy them before changing DNS zones.

TTL

TTL means Time To Live. It tells DNS resolvers how long they may cache a record before checking again.

Short TTL

  • Useful before migrations or planned changes.

Long TTL

  • Useful for stable records and lower DNS query load.

Common examples:

  • 300 seconds for migration window
  • 3600 seconds for normal records
  • 14400 seconds on many hosting defaults

Lower TTL before a migration, not after. Changing TTL after the switch does not clear old cached values immediately.

Why this matters

Why this matters

DNS zone management matters because one wrong record can break a website, email delivery, SSL issuance, verification or subdomains. In cPanel and Plesk, DNS changes are easy to make, but the panel does not always protect you from editing the wrong record.

Safe DNS management means understanding which provider is authoritative, backing up existing records, changing only what is needed and verifying results after propagation.

How to check DNS zone changes

Use DNS Lookup and related tools after editing records.

  1. Authoritative nameservers — Confirm where DNS is active.
  2. Website records — Check A, AAAA and CNAME records.
  3. Email routing — Check MX records.
  4. SPF — Confirm there is only one SPF TXT record.
  5. DKIM — Confirm selector records exist.
  6. DMARC — Confirm _dmarc record exists.
  7. SSL-related records — Check CAA or validation records if used.
  8. Propagation — Check again after TTL expires.

Verify DNS zone changes

Use DNS Lookup to confirm authoritative nameservers, A, CNAME, MX, TXT and other records after editing in cPanel or Plesk.

Run DNS Lookup →

Common problems

Editing DNS in the wrong place

High

The domain uses external nameservers, so cPanel/Plesk changes do not affect public DNS.

Next step: Check authoritative nameservers and edit DNS at the active provider.

Website A record points to old IP

High

Visitors still reach the old hosting server.

Next step: Update the A record to the correct hosting IP.

www points somewhere else

Medium

Root domain and www load different servers or content.

Next step: Align www CNAME/A record with the intended canonical setup.

MX records deleted during migration

High

Incoming email may stop working.

Next step: Restore MX records from the active email provider.

Multiple SPF records

Medium

More than one SPF TXT record can cause SPF validation errors.

Next step: Merge all sending sources into one SPF record.

DKIM selector missing

Medium

Outgoing mail may not be signed correctly.

Next step: Publish DKIM record exactly as provided by the email service.

DMARC missing

Low

The domain has less protection and reporting for spoofing.

Next step: Add a starter DMARC record and monitor results.

CNAME conflict

Medium

A hostname with a CNAME cannot normally have other records at the same name.

Next step: Remove conflicting records or use the provider’s recommended setup.

Wrong TTL during migration

Low

Changes may take longer to appear for some users.

Next step: Lower TTL before planned changes and wait for propagation.

Default zone reset removed custom records

High

Resetting a DNS zone can delete third-party service records.

Next step: Restore records from backup or provider documentation.

How to edit DNS zones safely

  1. Step 1: Confirm authoritative DNS

    Check which nameservers are active before editing records.

  2. Step 2: Export or copy current zone

    Save existing A, CNAME, MX, TXT, DKIM, DMARC and verification records.

  3. Step 3: Identify the exact record

    Decide whether you need to edit website, email, SSL or verification records.

  4. Step 4: Change only what is needed

    Avoid deleting unrelated records.

  5. Step 5: Use provider values exactly

    Copy hostnames, priorities, TXT values and targets carefully.

  6. Step 6: Check TTL

    Use lower TTL for planned migrations and normal TTL for stable records.

  7. Step 7: Verify after saving

    Use DNS Lookup, MX Lookup, SPF, DKIM and DMARC tools.

  8. Step 8: Monitor website and email

    Check website status, SSL and email delivery after DNS changes.

Safe DNS editing checklist

Use this checklist before and after saving DNS changes in cPanel or Plesk.

Confirm active nameservers

Edit DNS only where the domain is authoritative.

Copy current DNS zone

Save existing records before making changes.

Identify record type

Know whether you are editing website, email or verification records.

Confirm hostname/name field

Use the correct host or subdomain name.

Confirm target/value field

Copy IP addresses, hostnames and TXT values exactly.

Confirm TTL

Use lower TTL before planned migrations.

Confirm MX priority

Check priority values when editing email routing.

Confirm one SPF record

Avoid multiple SPF TXT records on the same domain.

Confirm DKIM selector name

Publish the selector record exactly as provided.

Confirm DMARC name is _dmarc

Use the correct DMARC hostname.

Avoid deleting verification TXT

Keep Google, Microsoft, CDN and tool verification records.

Avoid editing MX for website-only move

Do not change email routing unless email is moving too.

Screenshot old values

Keep rollback values before saving changes.

Check DNS externally

Verify records with DNS Lookup after saving.

Test website

Confirm homepage and important pages load correctly.

Test email

Send and receive test messages after DNS changes.

Check SSL

Confirm certificate issuance and HTTPS behavior.

Monitor for bounces or warnings

Watch email delivery and browser warnings after changes.

cPanel email routing note

In cPanel, MX records and Email Routing can both affect mail behavior.

Email Routing options may include:

  • Automatically Detect Configuration
  • Local Mail Exchanger
  • Backup Mail Exchanger
  • Remote Mail Exchanger

If email is hosted externally, Remote Mail Exchanger is often required. If the setting is wrong, the server may try to deliver mail locally instead of sending it to the external provider.

Nameserver migration warning

Changing nameservers moves DNS authority from one provider to another. This can affect every service on the domain, not only the website.

Before changing nameservers, copy:

  • A records
  • AAAA records
  • CNAME records
  • MX records
  • SPF record
  • DKIM records
  • DMARC record
  • CAA records
  • verification TXT records
  • subdomain records
  • autodiscover records

Do not switch nameservers until the new DNS zone contains all required records.

DNS zone examples

DNS zone examples 
Website record:

Name:
example.com

Type:
A

Value:
192.0.2.10

Purpose:
Point root domain to hosting server.

www record:

Name:
www

Type:
CNAME

Value:
example.com

Purpose:
Point www version to root domain.

Email routing:

Name:
example.com

Type:
MX

Priority:
10

Value:
mail.example.com

SPF:

Name:
example.com

Type:
TXT

Value:
v=spf1 include:_spf.examplemail.com ~all

DMARC:

Name:
_dmarc

Type:
TXT

Value:
v=DMARC1; p=none; rua=mailto:dmarc@example.com

Examples are illustrative. Use exact values from your hosting, email, CDN or verification provider.

Useful DNS checks

Useful DNS checks 
Check A record:
dig example.com A

Check www CNAME:
dig www.example.com CNAME

Check nameservers:
dig example.com NS

Check MX records:
dig example.com MX

Check SPF:
dig example.com TXT

Check DMARC:
dig _dmarc.example.com TXT

Check a DKIM selector:
dig selector._domainkey.example.com TXT

Trace DNS path:
dig +trace example.com

Commands are examples. Replace example.com and selector with your real domain and DKIM selector.

Frequently asked questions

What is a DNS zone?

A DNS zone is the collection of DNS records that controls services for a domain.

Where do I edit DNS in cPanel?

Usually in Domains → Zone Editor → Manage.

Where do I edit DNS in Plesk?

Usually in Websites & Domains → domain → DNS Settings.

Why do my cPanel DNS changes not work?

The domain may use external nameservers, so cPanel is not authoritative for public DNS.

Which records control the website?

Usually A, AAAA and CNAME records.

Which records control email?

MX controls incoming mail. SPF, DKIM and DMARC help authenticate outgoing mail.

Should I change MX records when moving a website?

No, not unless you are also moving email hosting.

Use these free tools to verify your configuration after applying changes.

DNS Lookup Domain Health Checker MX Lookup SPF Checker DKIM Checker DMARC Checker SSL Checker
Web Hosting vs Email Hosting: Key Differences 7 min read Migrating a Website to a New Host Without Downtime 9 min read Setting Up Your First VPS: Beginner Guide 10 min read Why Reverse DNS is Important for VPS Mail Servers 7 min read WordPress Email and DNS: SPF, DKIM and Deliverability Basics 8 min read
Browse all Hosting & VPS guides →

Need help applying this fix?

Send us your domain, report link or issue details. CheckDomainHealth will review the request and route it to the right technical team if hands-on support is needed.

Get Help Run Domain Health Check

Was this guide helpful?

Your feedback helps us improve our guides for everyone.