Panels & Zone Editors
The control panel is one of three possible homes for your DNS
You have edited a record in the panel, waited a day, and nothing has changed — this explains why.
The short answer
A control panel is the browser dashboard that runs a hosting account, and for anyone managing names its most misunderstood screen is the zone editor: the panel can hold a complete set of DNS records for your name and have absolutely no effect, because authority is decided by the NS records the registry publishes, not by which panel has a zone in it.
There are three candidate homes for your records — the registrar, the hosting panel, and an independent DNS provider — and exactly one of them is being read at any moment.
By the Hosting & Domains team · Reviewed 18 August 2026
0
Terms left unexplained
100+
Entries, each linked to its neighbours
Real
Examples, taken from live zones
Free
To read, with no account needed
Underneath, hosting is a collection of Linux services and configuration files. The panel lays menus over that machinery so the everyday jobs never need a terminal: files, databases, mailboxes, certificates, and a zone editor for names delegated to the host. cPanel leads the market; Plesk and DirectAdmin are the two other names worth knowing.
The panel you use also decides how portable you are. Backup formats, workflows and the muscle memory in your fingers all travel to any other host running the same panel, which is why the panel tends to outlive the contract with the company that supplied it.
Three candidates, one winner
Registrar DNS: the zone lives at the company you bought the name from, and hosting is reached by a single A record. Panel DNS: you have delegated the name to the host's nameservers, so the panel's zone is the live one. Third-party DNS: you have delegated to a provider whose only business is DNS, and both the registrar and the host hold nothing that anybody reads.
All three are respectable choices. What causes trouble is holding records in two of them and believing the wrong one, which is the single commonest DNS fault we see.
Proving which one is live
One command settles it: dig NS example.com +short. What comes back is what the registry publishes, and whichever nameservers those are is where your records have to be. Compare that answer with the nameserver names your host and your DNS provider each use.
If the delegation does not name the host's nameservers, the panel's zone editor is a scratchpad. Nothing you type there is wrong; it is simply never consulted, and it will sit there looking authoritative for years.
What each panel gives a name holder
cPanel has Zone Editor, plus a separate Email Routing screen that quietly decides whether mail for a name is delivered locally or handed onward. Plesk arranges everything by domain and applies a server-wide DNS template to new ones. DirectAdmin gives each domain its own DNS Management page and a mail toggle inside Domain Setup that rewrites the MX.
The three differ far more in wording than in function. Every one of them will let you break mail with a single well-intentioned tick.
The habit that saves the afternoon
Before editing any record, check delegation. It takes one command or one glance at the registrar's nameserver field, and it is the difference between a change that works in five minutes and a day spent doubting your own eyesight.
Second habit: verify from outside. The panel showing your new record proves the panel stored it. Only an outside resolver proves the world can see it.
Where your records live, before what they say
Almost every DNS problem that reaches our desk turns out to be a question of authority rather than syntax: the record was correct and stored in a zone nobody reads. So every entry here starts with which party holds the zone.
Hosting renews at the figure you ordered at, so year two costs precisely what year one did.
- The verifying command written out wherever one exists
- Neighbouring records and registry rules linked together
- Written by the people who answer the transfer tickets
- Locks and grace periods given in days, not folklore
Why Hosting & Domains
Standard on every plan
Authority established first
The one check that decides whether any record you write will ever be read, given in a single command.
A safe order of operations
Where a job has an order that avoids downtime, the order is spelled out: confirm authority, lower the cache, change one thing, verify from outside.
Three homes compared honestly
Registrar, panel and independent provider, with the reason somebody would sensibly choose each.
Short enough to finish in time
Each entry is written to be read through before the window you are worried about closes.
Panel wording decoded
The same function under three different names across cPanel, Plesk and DirectAdmin, matched up for you.
No stake in your conclusion
The mechanism is described the same way whether the sensible answer sends any business here or somewhere else entirely.
Quick Start
Order placed to site online
- 1
Read the delegation at the registry
dig NS on the name, or the nameserver field in the registrar's panel. Everything else depends on this answer.
- 2
Edit only in the zone that answers
Make the change where authority actually sits. A record in the wrong panel is not a small mistake; it is no change at all.
- 3
Confirm from a resolver you do not control
The panel showing the record proves storage. An outside lookup proves publication, which is the part that matters.
Built In
Fitted to every plan
- Staging copies, so a change is tried before the live name sees it
- No set-up charge at any point, and no joining fee
- The account live minutes after checkout
- The first year of the name included when the hosting plan is annual
- A zone editor in the panel, so the records stay yours to change
- Availability checked live before you pay for anything
- Spam and virus screening on every mailbox by default
- NVMe storage behind a LiteSpeed cache on every tier, the smallest included
- Softaculous in the panel for one-click installs, WordPress among them
- PHP versions chosen per site from the control panel
Frequently Asked
Questions we field again and again
I changed a DNS record in my hosting panel and nothing happened. Why?
Almost certainly because the name is not delegated to that host's nameservers, so the zone you edited is never queried. Run dig NS on the name and compare the answer with your host's nameserver names. If they differ, make the change wherever the delegation points instead — the registrar's DNS or a third-party provider — or move delegation deliberately, having first copied every record across.
Should DNS live at my registrar or in my hosting panel?
Either works; the question is which supplier you would rather be dependent on during a migration. Keeping the zone at the registrar means you can change hosts by editing one A record. Keeping it in the hosting panel means fewer places to look while the site and the mail are on the same platform. What you must not do is maintain both and lose track of which one the registry points at.
Can I keep DNS where it is and still host here?
Yes, and it is often the calmer option. Leave delegation with whoever holds it, then point an A record and the www record at the account. Authority stays wherever the NS records at the registry say it is, which also means the panel's own zone editor will have no effect until that changes.
Who stands behind Hosting & Domains?
Hosting & Domains is a trading name of Azaanex Inc., federally incorporated in Canada under company number 1766541-5, with terms governed by Ontario law. Running that check on any company before handing it a domain name is five minutes well spent.
Keep reading
WooCommerce Hosting
Store hosting with the certificate and mail records a checkout depends on.
WordPress Hosting
WordPress hosting where the site URL and the registered name are kept in step.
Changing provider? Work through this checklist beforehand.
A straightforward running order for a migration your visitors never spot: which files travel first, how to bring the mail across without dropping a single message, the right moment to repoint DNS, and the two errors that sit behind almost every outage we get called in to fix.
One panel, and records that actually answer.
Put the site on ground you own: free SSL, a free migration, and support that answers at any hour.
View WooCommerce Hosting plans