Zone editor notes · Beginner · 5 min per record
How to edit DNS records — Change the Record, Then Prove the Change Landed
You need one record changed without disturbing the four that are quietly holding your mail, your certificates and your verification tokens together.
The short answer
Edit the record in cPanel Zone Editor, then verify it with dig against a resolver you do not control — because the panel showing the new value proves only that the panel saved it. TTL is the number that decides how long a mistake lasts, so set it before you make the change rather than after.
Almost everything you will ever touch is one of five types: A and AAAA for addresses, CNAME for aliases, MX for mail with a priority, TXT for policy and proof, CAA for which authority may issue a certificate. Learn what each one answers and the panel stops being intimidating.
By the HostingFast team · Reviewed 24 August 2026
Beginner
Skill floor
5
Stages start to end
Free
Support, every tier
Proven
Run on the live stack
You need cPanel access and about five minutes per record. Zone Editor sits under the Domains section and lists every row currently answering for the domain.
Every edit here is reversible; the cost of reversing it is one TTL. That is the whole reason the TTL column matters more than it looks.
The five types that do almost all the work
A maps a hostname to an IPv4 address and AAAA does the same for IPv6. CNAME says 'ask about this other name instead', which is why it cannot sit at the apex alongside SOA and NS. MX names the mail servers and carries a priority, where lower wins. TXT holds text that other systems read: SPF, DKIM, DMARC and verification tokens.
CAA is the one most people have never edited and should know about. It lists which certificate authorities are permitted to issue for the domain, so a CAA row that names only one authority will quietly block AutoSSL from a different one. If a certificate refuses to issue and DNS looks fine, check CAA before anything else.
TTL is your rollback window, not a detail
TTL is how many seconds a resolver may keep an answer before asking again. It is therefore exactly how long your mistake stays live after you have fixed it. A record at 14400 has a four-hour tail; the same record at 300 has a five-minute one.
The working pattern is: lower the TTL, wait out the old value, make the real change, then raise it again once things have settled. Day to day, 3600 is a reasonable resting value for records that rarely move. Leaving everything at 300 permanently means every visitor pays for a fresh lookup that gains them nothing.
Host expansion, trailing dots and the doubled domain
cPanel appends the zone name to anything in the Name field that is not fully qualified. Type www and you get www.yourdomain.com, which is what you wanted. Type www.yourdomain.com and you may get www.yourdomain.com.yourdomain.com, which is not, and the panel will show it back to you looking almost right.
The same trap catches record values. A CNAME or MX target that points at another domain needs the trailing dot to be fully qualified. Paste, then read the saved row back character by character — the doubled suffix is the single most common reason a token verifies nowhere.
Why the browser is the worst test you have
Your browser sits behind its own DNS cache, the operating system resolver, possibly a corporate resolver and your ISP's. A page that still loads the old way tells you nothing about whether the record changed. Ask DNS directly instead: dig TXT yourdomain.com @1.1.1.1 and dig MX yourdomain.com @8.8.8.8.
Query the authoritative nameserver too, with dig @ns1.yourprovider.example +norecurse, because that answer is the truth and everything else is a copy of it with a countdown attached. When authoritative is right and a public resolver is wrong, you are not debugging, you are waiting.
The stack these steps were measured on
Every walkthrough here is run against the platform we operate — cPanel, LiteSpeed in front of NVMe, Softaculous, WP-CLI over SSH — so the field names in the instructions are the field names on your screen.
Every plan includes an SSL certificate that reissues itself before expiry, so the padlock is never something you have to diarise.
- Record types explained by what they answer
- TTL treated as the recovery time it is
- Verification commands, not hopeful refreshing
- Engineers on support at any hour
Why HostingFast
Standard on every plan
Types by function
Each record type is introduced by the question it answers, which is what makes the Zone Editor readable rather than intimidating.
TTL as a first-class number
The page treats TTL as your rollback window and gives you a working pattern for lowering and restoring it around a change.
The expansion trap named early
Host expansion and missing trailing dots produce a doubled domain that looks nearly right, so it is called out before you paste anything.
5 steps, no padding
Five actions, each ending in something you can observe, and the CAA check that saves certificate debugging later.
Verified against DNS itself
The last step queries authoritative and public resolvers rather than reloading a page and hoping.
Engineers on call
If a record will not take or a certificate will not issue, support answers at any hour with the cause rather than a link.
Quick Start
From order to online
- 1
Open Zone Editor and filter to the type
In cPanel, go to Domains and then Zone Editor, choose Manage for the domain and filter by record type. Read the existing rows before you change anything, and note the TTL column — that is the number the rest of this job is planned around.
- 2
Lower the TTL first, then wait out the old value
Set the record you intend to change to 300 seconds and leave it for at least as long as its previous TTL. Resolvers then hold a short-lived answer when the real change lands, which is what turns a four-hour mistake into a five-minute one.
- 3
Paste the value, never retype it
Copy the target from the source and paste it in. IPv4 addresses, DKIM keys and verification tokens are exactly the strings a human eye skips over, and a transposed character produces a record that looks correct and answers wrongly.
- 4
Read the saved row back, suffix included
After saving, check how the panel expanded the Name field and whether the value kept its trailing dot. If you see yourdomain.com.yourdomain.com anywhere, fix it now: nothing downstream will ever find that record.
- 5
Verify against authoritative, then a public resolver
Run dig +noall +answer TYPE yourdomain.com @ns1.yourprovider.example +norecurse for the truth, then the same query against 1.1.1.1 and 8.8.8.8 with the TTL countdown as your progress bar. Only then check the application that needed the record.
Built In
Loaded onto every plan
- No setup fee on any plan, at any tier
- Webmail in the browser plus IMAP, POP and SMTP
- Daily backups with self-service restores from the panel
- DDoS filtering absorbed at the network edge
- WordPress and 400+ other applications in one click
- LiteSpeed caching in the server, not bolted on by plugin
- Per-site PHP version switching in the control panel
- cPanel, the control panel most of the industry already runs
- Money back: 30 days on hosting, 7 on reseller
- A renewal price identical to the one you signed up at
Frequently Asked
What people ask us most often
Why does my TXT record show the domain twice?
Because the Name field was already fully qualified and cPanel appended the zone to it anyway. Enter the host part alone — @ or a bare label such as _dmarc — and let the panel add the rest. If the row already reads _dmarc.yourdomain.com.yourdomain.com, delete it and recreate it rather than editing around it, and confirm with dig that the name you expect is the name that answers.
What TTL should I use day to day?
3600 is a sensible resting value for records that rarely change: long enough that resolvers do real caching, short enough that an emergency costs an hour rather than half a day. Drop to 300 deliberately before a planned change and put it back afterwards. A zone left permanently at 60 makes every visitor pay for lookups and buys you nothing on a quiet week.
Can I point two CNAMEs at the same hostname?
You can have many CNAMEs pointing at one target, but you cannot have two CNAME records on the same name, and a name with a CNAME may not carry any other record type. That is the rule that bites when someone adds a CNAME to a host that already has an MX or TXT row: use A records on that host instead, or move the alias to a name of its own.
Does Zone Editor let me set a CAA record?
Yes, CAA is in the type list alongside A, CNAME, MX and TXT. It is worth checking even if you never set one, because an inherited CAA row that names a single certificate authority will block AutoSSL from issuing through a different one and the error message rarely says so. Query it with dig CAA yourdomain.com when a certificate refuses to appear.
Keep reading
How to Choose a Domain Name
Choose the name that is cheapest to type, say and paste before you commit to it for years.
How to Monitor Website Uptime
Watch the apex from outside, with a check interval that catches a short outage rather than reporting it late.
DNS Propagation (Glossary)
The definition this page leans on, with the TTL countdown explained.
Web Hosting
cPanel hosting on NVMe with LiteSpeed caching from the entry tier upwards.
Laravel Hosting
Laravel hosting with the PHP version, Composer and queue tooling already in place.
Changing hosts? Run through our checklist first.
A straightforward sequence for a switch your visitors never feel: which files move first, how to shift email across without losing a single message, the right moment to repoint DNS, and the two mistakes behind almost all the downtime we get asked to rescue.
Edit records on quicker hardware.
NVMe behind a LiteSpeed cache, free SSL, free migration, and a renewal price identical to the one you signed up at.
View Web Hosting plans