All Systems Operational|support@delhihosting.com
cPanel · In-depth guide

How to Manage DNS With the Zone Editor

16 Mar 2026 · 10 min read · DelhiHosting Team

DNS is the address book of the internet — it tells the world where to find your website and deliver your email. Most “my site/email suddenly stopped” problems trace back to one DNS record. This guide explains the records that matter, how to edit them safely in cPanel’s Zone Editor, and how to avoid the mistakes that take sites offline.

How DNS works, briefly

When someone visits your domain, their device asks DNS “where is this?” and DNS replies with a server address. Different record types answer different questions — where the website is, where email goes, and so on. Edit these in cPanel under Zone Editor.

The records you’ll actually touch

RecordPoints…Used for
Aa name → an IPv4 addressYour website (the core record)
AAAAa name → an IPv6 addressIPv6 website access
CNAMEa name → another nameSubdomains, www, third-party services
MXyour domain → a mail serverEmail delivery
TXTplain text valuesSPF, DKIM, DMARC, domain verification
The big four
Ninety percent of real-world DNS issues involve an A record (site won’t load), an MX record (email won’t arrive), or a TXT record (mail going to spam). Know these three and you can diagnose most problems.

Editing a record safely

1
Open Zone Editor
In cPanel’s Domains section, open Zone Editor and click Manage for your domain.
2
Note the current value
Before changing anything, copy the existing value somewhere so you can revert instantly if needed.
3
Edit one record
Change only the record you mean to. For example, to move your site to a new server, update the A record to the new IP.
4
Save and wait
Save, then allow time to propagate — changes are not instant.

Propagation: why changes aren’t instant

DNS changes spread across the internet gradually, governed by each record’s TTL (time to live). Expect anywhere from a few minutes to a couple of hours, occasionally up to 24–48. If something looks wrong immediately after a change, wait before assuming it failed — and lower the TTL before a planned migration so changes apply faster.

Common DNS tasks and fixes

GoalRecord to change
Move website to a new serverA record → new IP
Point www to your siteCNAME www → your domain
Use Google Workspace emailMX records → Google’s, routing → remote
Stop email going to spamAdd/fix SPF, DKIM, DMARC (TXT)
Verify a service (Search Console etc.)Add the provided TXT record

Mistakes to avoid

Key takeaway

A records point your site, MX records route your email, and TXT records authenticate it. Edit one record at a time in Zone Editor, note the old value first, and allow time to propagate — and most DNS problems become easy fixes.

Frequently asked questions

Usually minutes to a couple of hours, occasionally up to 24–48. Lowering a record’s TTL before a planned change makes it apply faster.

Either the A record still points to the old IP, or the change hasn’t propagated yet, or your browser/computer cached the old DNS. Verify the A record, then wait and flush your DNS cache.

You likely altered or removed an MX record, or changed email routing. Restore the correct MX records and ensure routing matches where your mail is hosted (local or remote).

Time To Live — how long servers cache a DNS record before re-checking. Lower it before planned changes so updates take effect quickly; raise it afterwards to reduce lookups.

Related cPanel guides

Want us to handle this for you?

Our Delhi-based engineers set up, secure and optimise hosting for you — with free migration and real human support.