PD Plesk DNS — Plesk Zone & Record Management for WHMCS
Manage your Plesk DNS zones and records inside WHMCS — fast, self-service, auto-provisioned
Made and supported by Projektif Digital Ltd.
Runs inside PD Modules, the panel
every module installs into.
Domains & DNSBETA
Connect your Plesk server once — every DNS zone loads automatically with an instant health check, so you know the connection works before you go live.Customer self-service DNS portal — clients manage their own zones from inside WHMCS without opening a support ticket, on any bundled theme including Six (Bootstrap 3).The same self-service portal on Twenty-One (Bootstrap 4) — one implementation, every WHMCS theme, no custom CSS needed.1 / 3
PD Plesk DNS lets a hosting company manage the DNS zones on its Plesk servers from inside WHMCS, 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 WHMCS 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 hosting service to its client. Nothing changes on Plesk.
Open it to customers. A Manage DNS link appears on the domain and service pages of clients whose domain has a zone.
The Providers page, with the Plesk server connected and the registrar-DNS takeover list
What you get in WHMCS
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 products
Auto-provision, off by default: a zone is bound to the client when a domain is registered or transferred, or a service with a domain is set up. 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 WHMCS's own cron
Orphaned zones are flagged and never deleted automatically
What your customers get
Manage DNS in your client area, rendered natively on Six, Twenty-One and Nexus
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
The customer's Manage DNS page on the Six themeThe same page on the Twenty-One theme
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 WHMCS 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
WHMCS 9 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
Questions
Does PD Plesk DNS store my DNS records?
No. PD Plesk DNS reads records live from your Plesk server and writes changes back immediately. Plesk remains the authoritative source of truth. The module stores only metadata — zone ownership, backup snapshots and activity logs — in your WHMCS database.
What version of Plesk do I need?
PD Plesk DNS works with a Plesk Obsidian server that has the XML-API enabled. Connect using a Plesk API secret key — created under Tools & Settings, API Keys — which is preferred, or the admin username and password. An API key can be rotated without changing the admin password.
How do I connect my Plesk server?
Enter your Plesk host, an API secret key (or admin username and password) and, if you use a non-standard port, the API port — the default is 8443. Credentials are stored encrypted and shown masked. That is the only setup step; every DNS zone loads straight away.
Does deleting a zone in WHMCS delete it from Plesk?
No. Plesk removes a DNS zone with its domain or subscription, so this module never deletes one: **Delete zone** in a zone's ⋯ menu, the orphan setting **When cleaning an orphan, also delete the zone at the provider** and turning off **Keep the DNS zone when a service is terminated** all say that the zone has to be removed in Plesk and leave it in place. Removing a provider, cleaning up an orphan and terminating a service otherwise leave the zone untouched.
What record types are supported?
A, AAAA, CNAME, MX, TXT and NS, each with a type-aware editor that checks addresses and hostnames before saving.
Is DNSSEC supported?
DNSSEC management is not offered for Plesk in this module. If you need DNSSEC on a zone, use Plesk's own DNSSEC tooling on the server. Everything else — records, backups, auto-provisioning and customer self-service — is fully managed inside WHMCS.
What happens to zones if my subscription lapses?
DNS records are never touched on lapse — your zones and records stay exactly as they are and keep being served. Management steps down in stages: admin management locks first while your customers keep their own DNS self-service, which stops only later, behind a neutral 'temporarily unavailable' message. Renewing restores everything.
Can I auto-create zones when domains are registered?
For domains already on the server, yes: enable 'Automatically create a DNS zone on registration and new services' in Settings. Its zone is linked to the customer when a domain is registered or transferred, or a service with a domain is set up. Plesk creates a zone with its domain or subscription, so a domain that is not on the server yet is reported in Activity, not created. Separately, the TLD takeover list on your provider names the extensions whose nameservers are also pointed at Plesk when such a domain is registered or transferred (registrar modules that support nameserver changes).
What does it cost to run, on top of the subscription?
Only what you already pay your provider. PD Plesk DNS adds no per-unit fee and takes no cut — it connects to your own account with your own credentials, so the provider bills you directly at your rates, and you set what you charge your customers. From us it is the module subscription and nothing else.
Which WHMCS and PHP versions does it need?
WHMCS 9 or later, on PHP 8.2 or later. It installs alongside whatever else you run — it adds its own tables and templates rather than modifying WHMCS files, so it does not collide with other vendors' modules or with a customised theme. Uninstalling removes its own tables and settings and leaves no orphans behind.
What’s new in 0.1.104
No TTL box Plesk ignores, and no Create or Delete zone: Plesk handles zones with the domain.
Featured
