cPanel Zone Editor: Add, Edit, and Delete DNS Records

If you host with cPanel, the Zone Editor is where almost every DNS change actually happens — pointing a subdomain, adding a verification TXT record, fixing a typo in an MX entry. It's a simple tool once you know where it lives, but the interface has quirks that trip people up, and "why isn't my change working" is one of the most common tickets we see. Here's how to use it properly, and what to check when it doesn't behave.

Where to Find the Zone Editor

Log in to cPanel and search for Zone Editor in the top search bar, or find it under the Domains section. You'll see a list of every domain and subdomain on the account, each with a Manage button. Click it for the domain whose DNS you want to change — not the domain that happens to be selected by default, which trips people up when they're managing an addon domain.

One thing worth checking before you touch anything: the Zone Editor only controls DNS if your domain's nameservers actually point at this cPanel server. If you're using Cloudflare, your registrar's DNS, or a different host's nameservers, editing records here does nothing — the real zone lives elsewhere. Run dig NS yourdomain.com +short from a terminal if you're not sure who's authoritative.

Adding a New DNS Record

Inside a domain's Zone Editor, click + Add Record and pick the record type from the dropdown. The form changes slightly depending on type, but the core fields are the same:

• Name — the hostname, e.g. @ for the root domain, www, or mail. cPanel usually appends the full domain automatically as you type.
• TTL — how long (in seconds) resolvers should cache the record. 14400 (4 hours) is the cPanel default; drop it to 300 before a planned change so old data expires fast.
• Type — A, AAAA, CNAME, MX, TXT, SRV, CAA, and a few others.
• Record / Value — what the record points to: an IP for A/AAAA, a hostname for CNAME/MX, a text string for TXT.

Click Save Record and it's live in the zone file immediately — propagation delay is a separate matter, covered below.

Quick Reference: What Each Record Type Needs

Editing an Existing Record

Every record in the list has an Edit link on the right. Click it, change the TTL or value, and hit Save Record. A few things to watch for here:

• You generally can't edit the NS or SOA records for the domain from this screen — those are managed separately and editing them incorrectly can break the whole zone.
• If you're editing an MX record, make sure the priority number is right. Lower numbers are tried first — a stray 0 on a backup mail server will steal all your inbound mail.
• Editing a record doesn't reset its TTL countdown for resolvers that already cached the old value — they'll keep using the stale answer until their own cached TTL expires, regardless of what you just set.

Deleting a Record

Click Delete next to any record and confirm. There's no undo, so if you're not sure what a record does — especially an SRV, CAA, or a TXT you didn't add yourself — copy its value somewhere before removing it. We've had customers delete an old SPF or DKIM TXT record that turned out to still be feeding a legacy mail relay, and mail delivery quietly broke a few days later when the old TTL finally expired.

Symptom: Changes Aren't Taking Effect

You saved the record, refreshed, and the site or email behavior hasn't changed. Before assuming the Zone Editor is broken, check these in order:

Cause 1: You're editing the wrong zone

If the domain uses external nameservers (Cloudflare, GoDaddy DNS, another host), the cPanel zone file is irrelevant — nothing you save here is ever queried. Confirm with dig NS yourdomain.com. If the output doesn't show your hosting provider's nameservers, you need to make this change at the actual DNS provider instead.

Cause 2: DNS caching, not a save failure

Resolvers, ISPs, and even your own OS cache DNS answers for the old TTL duration. A record you just changed from a 4-hour TTL can take up to 4 hours to update everywhere. Test with dig recordname.yourdomain.com @8.8.8.8 to bypass your local cache and query Google's resolver directly.

Cause 3: The account is on a DNS cluster

On some multi-server setups, DNS is synced across a cluster of nameservers via WHM. If the sync job is delayed or failed, one nameserver can serve the new record while another still answers with the old one — which looks exactly like flaky propagation. This is a server-side issue your host needs to check in WHM's DNS Cluster status, not something you can fix from cPanel.

Zone Editor Missing or Grayed Out

If the Manage button is disabled or the page shows no records at all, it's almost always one of these:

• The domain isn't actually hosted on this account — it was added as a parked or addon domain pointing elsewhere, or removed but not cleaned up from DNS.
• Your hosting plan or reseller account has DNS management restricted by the provider (common on shared reseller setups where the parent account controls DNS centrally).
• The zone file itself is corrupted, usually after a botched manual edit via SSH or an interrupted server migration — this needs a support ticket to rebuild.

Prevention: A Few Habits That Save Tickets

• Lower the TTL to 300 seconds a day before any planned DNS change (server migration, mail provider switch), then raise it back to the default once things are stable.
• Keep a plain-text copy of your zone — export it or just screenshot the record list — before making bulk changes. It's the fastest way to undo a mistake.
• Never delete a TXT or MX record you don't recognize without checking what's using it first. SPF, DKIM, and third-party service verification records are easy to mistake for clutter.
• If you manage multiple domains on the account, double-check you're editing the one you think you are — the domain selector at the top of Zone Editor doesn't always match what you expect after switching accounts.

The Zone Editor itself rarely breaks — most "it's not working" cases trace back to editing the wrong zone or waiting out an old TTL. Once you know which of those you're dealing with, the fix is usually just patience or a five-minute correction, not a rebuild.