Panels & Zone Editors
Plesk organises hosting around the domain, which suits name holders
You manage a dozen names and want a panel where each name's records, mail and certificate sit in one place.
The short answer
Plesk is a major control panel with two distinguishing features for anyone managing names: it arranges everything under the domain rather than under the tool, so one name's DNS, mail and certificate sit together on one card; and it runs on Windows servers as well as Linux, which makes it the practical choice wherever ASP.NET or MSSQL is involved.
Feature for feature it stands level with the alternatives. The domain-first arrangement is not a small thing when your unit of work is a name rather than a server.
By the Hosting & Domains team · Reviewed 18 August 2026
100+
Terms defined for people who hold names
2 min
To read, at an unhurried pace
Plain
English, with the registry jargon translated
24/7
Cover on the support desk, all year
Sites, mail, DNS, databases and certificates are all present and all reached by opening the domain first. People who think in names navigate it faster than a wall of tool icons; people who think in servers sometimes find it fussy. Both reactions are about the arrangement rather than the capability.
Because it also runs on Windows, Plesk turns up wherever a Microsoft stack does — and Microsoft-shaped mail brings its own records, notably the autodiscover entry that mail clients look for before anybody has typed a server name.
One card per name, records included
Each domain in Plesk carries its own DNS settings, its own mail settings and its own certificate, which means an audit of one name is one screen rather than four. For a portfolio that difference compounds: checking twelve names for a stray MX takes twelve clicks rather than a spreadsheet.
The same grouping makes the authority question harder to dodge, which is a virtue. Plesk shows the zone it holds next to the name it holds it for, so a zone that nobody queries is at least visible in context.
The DNS template, and what it will not do
Plesk keeps a server-wide DNS template that new domains inherit. Add a record to it and every subsequently created domain gets that record; existing domains do not, unless you deliberately apply the template to them, which overwrites local changes.
So the template is a good place for something every name needs — a verification record for a mail provider you always use — and a bad place to experiment. Apply it to one domain first and read what changed before you apply it to forty.
Windows names and the records they expect
A Microsoft-oriented mail setup usually wants an autodiscover record, commonly a CNAME, so that clients configure themselves. Miss it and mail still works while every user is asked for server names they do not have. It belongs in whichever zone is authoritative, which on a Plesk-hosted name may or may not be Plesk.
The same applies to the SRV records some services publish. They are ordinary records in an ordinary zone; only the naming convention makes them look exotic.
Moving a name between panels
Delegation does not care which panel serves the name, so a move between Plesk and any other panel is a rebuild of the zone rather than a change of registration. The records are portable; the zone file format is not always.
Export the records first, rebuild them at the destination, compare the two lists line by line — MX, TXT, autodiscover, everything — and only then change delegation. Panels differ in what they add for you, and the differences show up in the comparison.
A panel that thinks in names, described that way
Most Plesk explanations are written for people choosing a server. This one is written for people holding a dozen names who want to know how quickly they can audit them, and where the DNS template will help or bite.
A free SSL certificate comes with every plan and reissues itself before the old one lapses.
- Registry, registrar, reseller and host kept distinct throughout
- The verifying command written out wherever one exists
- Neighbouring records and registry rules linked together
- Written by the people who answer the transfer tickets
Why Hosting & Domains
Standard on every plan
Auditing a portfolio quickly
Why one card per name matters when your job is checking twelve names for one stray record.
Clocks stated in days
Locks, grace periods and cache lifetimes are given as numbers you can diarise instead of being left as folklore.
Templates handled carefully
What a server-wide DNS template reaches, what it does not, and the order that keeps it from overwriting good records.
Linked by mechanism, not keyword
Each entry points at the record type, the panel screen or the registry rule it depends on, so one lookup leads to the next useful one.
Autodiscover named
The record Microsoft-shaped mail clients look for, where it belongs, and what its absence feels like.
The failure mode named first
Every entry says what breaks earliest when the job goes wrong, and the answer is very often email.
Quick Start
Order placed to site online
- 1
Open the domain, then the tool
Plesk's logic runs name-first. Working with it rather than against it is the whole learning curve.
- 2
Apply a template to one name before forty
Read exactly what the application changed on a single domain. Templates overwrite local edits without asking twice.
- 3
Compare zones line by line before delegating
Export the old records, rebuild them, then diff the two lists. Panels add different things for you, and the diff is where you find out.
Built In
Fitted to every plan
- Softaculous in the panel for one-click installs, WordPress among them
- PHP versions chosen per site from the control panel
- DDoS filtering absorbed at the network edge
- ImunifyAV+ sweeping every site on the account for malware
- WebP image optimisation built in, at no extra charge
- Free SSL on every plan, reissued before the old certificate lapses
- Auto-renew switched on or off name by name from the account
- Webmail in the browser, with IMAP, POP and SMTP for any client you prefer
- The latest cPanel, with people on the support desk at any hour
- Your site lifted off the old host and set down here, at no charge
Frequently Asked
Questions we field again and again
Does moving from Plesk to another panel affect my domain registration?
Not at all — the registration lives at the registry and is untouched by anything a panel does. What moves is the zone: the records have to be rebuilt at the destination and delegation pointed there once they match. Export the records, rebuild, compare the two lists including TXT and autodiscover entries, and change nameservers last. The name itself never enters the conversation.
Why does Plesk keep a DNS template, and when does it hurt?
It exists so every new domain starts with a sensible zone rather than an empty one, which saves real time on a server carrying many names. It hurts when applied retroactively: applying the template to an existing domain replaces its zone with the template's version, taking your local edits with it. Apply it to one name, read the result, then decide.
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.
Is a name's renewal price the same as its first year?
For the hosting, yes: it renews at the figure you ordered at. For the name, not necessarily — each registry sets its own renewal rate, and on plenty of extensions the second year costs more than the first. The figure shown against the name at checkout is the one that will be billed, so read it before a cheap first year persuades you.
Keep reading
CMS Hosting
CMS hosting with the records a content platform expects already accounted for.
Drupal Hosting
Drupal-ready hosting with the PHP and database headroom the platform asks for.
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.
A panel arranged the way you already think.
From one website to a rack of machines, moving up is a change to the account rather than a migration.
View CMS Hosting plans