PD Plesk DNS lets a hosting company manage the DNS zones on its Plesk servers from inside Blesta, and lets its customers change their own records from a Manage DNS area in the client portal. Every zone on the server is listed against the client and domain it belongs to, edits go straight to Plesk, and your customers never get a Plesk login.
It is built for hosts who serve DNS from Plesk and want billing and DNS in one place: staff stop switching panels to answer a record request, and customers stop raising tickets for them.
Why hosts choose PD Plesk DNS
One key, one connection. Add your Plesk hostname, port and API key once, press Test connection, and every zone the key can see appears with no import or sync step. Connect as many Plesk servers as you run and work across them in one list.
Plesk stays the source of truth. Records are read live from Plesk and written back when you save. The module keeps no copy of them, so Blesta never shows a record Plesk is not serving.
Built around how Plesk keeps DNS. Plesk holds a zone with its domain or subscription, so the module manages the zones of domains that exist in Plesk. Create zone and Delete zone explain that and do nothing: the zone arrives with its domain, and no setting of the module deletes a zone at Plesk. Where the module edits a record, Plesk applies it as remove-and-recreate, so the record gets a new id.
Customers do the small jobs themselves. Adding an MX record for new mail, a TXT record for a verification or a CNAME for a subdomain is something customers do on their own zones, with an editor that shows only the fields their record type needs and checks the values before saving.
Control over what customers can do. Lock a zone, cap how many zones and records a package allows, set blocked-content patterns and IP allow and deny lists, or make the zones of domains registered with you but not hosted with you view-only or hidden.
Backups and recovery. Zones are snapshotted on a schedule as BIND zone files. Any snapshot can be downloaded or restored, and a zone deleted by mistake can be recreated with every record it had.
How it works
- Create a Plesk API key. In Tools & Settings, create the key and bind it to your billing server's IP address. Plesk shows the value once.
- Add the server. In Providers, enter a name, hostname, port and the key, then press Test connection. It says whether Plesk can be reached and what to fix if not.
- Link zones to clients. Track matched zones binds each zone that matches an active domain or service to its client. Nothing changes on Plesk.
- Open it to customers. Their zones appear on the DNS page under My Tools in the client portal.
What you get in Blesta
Zones and clients
- Zones listed from Plesk with client, the domain or service they are bound to, nameservers, health, sync state and last backup
- Search by name and filter by provider, tracking state, status or client with a client picker, paged on the server
- Assign a zone to a client and, optionally, one of their domains or services
- Lock a zone to stop the client's own changes while you keep full control
- Untracked zones on the server are flagged, and Track adopts one without changing it
- Reconcile and health jobs flag zones that have gone missing or whose owner is no longer active
- Point chosen domain extensions at your Plesk server, so nameservers are set when such a domain is registered or transferred
Records
- Type-aware editor: every record type Plesk lists gets exactly the fields it needs, such as priority and mail server for MX
- Search by name or value, filter by type, and choose 10, 25, 50 or 100 per page
- Delete asks for confirmation and removes that one record, leaving other values at the same name
- Templates with merge fields, applied in one click and safe to apply twice
- Import a BIND zone file with a count of the new records before anything is written, and export any zone as a zone file
Limits and automation
- Packages cap zones per customer and, optionally, records per zone and per type, linked to your packages
- Auto-provision, off by default: a zone is bound to the client when a domain, or a service with a domain, is activated. A failure is logged and never interrupts the order
- REST API with named tokens, read or write scope, optional IP limits and 120 requests a minute, with every write recorded in Activity
- Activity shows who changed what, when, and whether it worked
- Optional email notices to customers and admins, all off until you switch them on
Backups and upkeep
- Scheduled snapshots every 24 hours by default, keeping the newest 10, both adjustable
- Back up one zone or every zone on demand, and restore any snapshot after a safety snapshot
- Maintenance page to run sync, health check, orphan check and backups, using Blesta's own cron
- Orphaned zones are flagged and never deleted automatically
What your customers get
- Manage DNS in your client portal, reached from My Tools in the client menu, with each zone's pages as tabs on the page
- A checked editor to add, edit and delete records on their own zones, and only their own
- Quick set-ups for Google Workspace, Microsoft 365 and an SPF lockdown, adding only what is missing and never a second SPF record
- Zone files: import and export a BIND zone file
- Their own snapshots, taken, downloaded and restored by themselves
- Wording you control: every string is translatable and overrides survive updates
Customer pages never show your server address or key, and never name the server behind their DNS.
Security built in
- The API key is stored with authenticated encryption and is never shown again in the provider form
- It is used only to read and update zones and records
- Customers reach only zones bound to their own account, enforced on the server
- Rotate the key by creating a new one in Plesk, entering it on the provider and testing it. Then delete the old one
One product, every feature
PD Plesk DNS is one paid module with everything included and no per-zone or per-seat fee. It installs into PD Modules, updates itself, and uninstalls without leaving tables behind or touching Blesta files.
What it does not do: it does not sign zones or manage DNSSEC keys, so there is no DNSSEC control. It is listed as beta: it is built on Plesk's official API and checked against that API's documented behaviour, and it leaves beta as results from hosts' live servers come in. If your subscription lapses, DNS records are never touched and Plesk keeps serving every zone.
Requirements
- Blesta 6.0 or later on PHP 8.2 or later, with the ionCube Loader
- A Plesk server with an API key (Plesk 12.0 or later; Plesk Obsidian is recommended)
- PD Modules, the free control panel every PD module installs into
Featured
