PD DNS Manager for WHMCS

PD DNS Manager lets a hosting company run DNS for its customers on whatever DNS service it already uses, or several at once, from one screen in WHMCS. Connect Cloudflare, AWS Route 53, cPanel/WHM, Plesk, DirectAdmin, DigitalOcean, Google Cloud DNS, Azure DNS, OVH, Hetzner DNS, Gandi LiveDNS, deSEC, DNSimple, Vultr DNS, PowerDNS or BIND 9. Your staff and your customers get the same zone and record editor on every one of them, inside your own WHMCS and your own theme.

It is built for hosts and registrars whose DNS is spread across more than one provider, or who expect to change provider one day, and who do not want a different tool, a different login and a different support answer for each.

Why hosts choose PD DNS Manager

One module for every DNS backend. Most DNS modules drive a single provider, so a host with Cloudflare for some customers, a cPanel cluster for others and a PowerDNS server of its own ends up with three modules, three sets of screens and three sets of training. PD DNS Manager drives sixteen backends through one interface, and you can connect more than one account of the same provider too.

Change provider without a customer noticing. Mark a provider "Existing domains only" and it keeps serving every zone it has while new zones go to the next provider that accepts them. When you are ready to leave it, move zones between providers with a dry run first: it shows what will be copied, what is skipped by record type, what has a TTL raised and where DNSSEC needs attention. The source is never changed, every record is verified at the target, and management moves only for zones that verified.

A second copy of your DNS. A replication pair mirrors every zone of one provider onto another, record by record, hourly or on demand.

Nothing to import. Zones and records are read live from the provider, with no local copy to drift out of date. If a provider already holds zones, they are listed straight away. Track matched zones binds every one that matches an active domain or hosting service to the right client in one go, and nothing is changed at the provider.

DNS that sets itself up. With auto-provision on, a zone is created at your default provider when a domain is registered or transferred, or a service with a domain is set up, and a Manage DNS link appears on that client's pages. If a server refuses at that moment, for example a control panel that cannot yet see the new delegation, the domain is queued and retried every 15 minutes at first, then less often, for up to seven days. The customer is told once, when it works.

Your customers stop opening tickets. They edit their own records, turn on DNSSEC, import and export zone files, take and restore their own backups and set up Google Workspace or Microsoft 365 in a click, all in your client area.

How it works

1. Connect your providers. Choose a backend, enter its credentials and press Test connection, which says whether the module can reach the account and what to fix if it cannot. Pick a default provider for new zones.
2. Decide how zones appear. Switch on auto-provision, choose which extensions you host DNS for and let the module point nameservers at you when those domains are registered or transferred, or create zones by hand.
3. Set the rules. Create quota packages and link them to your WHMCS products, add record templates and set the content policies customers must stay inside.
4. Your customers take over. They manage their own zones from your client area, and every change is logged with who made it.

What you get in WHMCS

Providers and zones

• Sixteen backends, several at once, each with a Test connection before you save
• A default provider for new zones, and an "Existing domains only" setting to retire one gracefully
• Zones list with search and filters by provider, tracking state, status and client; paged on the server so it stays fast with thousands of zones
• Each zone shows its client, the domain or service it belongs to, nameservers, health, sync and DNSSEC state, whether client edits are locked and when it was last backed up
• Create zone, assign a zone to a client with a searchable picker, lock a zone against customer changes, and delete a zone only after a confirmation
• Zones with a client picked list that client's active domains and services that have no DNS zone yet, each with a one-click Create zone
• Untracked zones are flagged, and Track matched zones adopts them without touching the provider

Records

• A type-aware editor that shows only the fields a record type needs, and checks addresses and hostnames before anything reaches the provider
• Records are read live and written straight back, with search, type filter and server-side paging that reaches every record of a very large zone
• Import a BIND zone file with a preview of how many records will be added; export any zone as a BIND file
• DNSSEC switched on per zone with one button, with the DS record shown ready to copy for the registrar
• Record templates with merge fields such as {domain}, {ip} and {ns1} to {ns5}, applied from a zone's menu; applying twice is safe
• Bulk operations that add, update or delete a record across many zones in the background, with per-zone results kept
• Website and email forwarding for domains with no hosting, on providers that support it, with a warning before a forward overrides a host already in real use

Selling and controlling DNS

• Quota packages that cap how many zones a customer may have and how many records a zone may hold, including a cap per record type with a default TTL, linked to the WHMCS products you sell
• Content policies: blocked content patterns, and allow and deny lists for the addresses a customer's A and AAAA records may point at. They apply to customer saves, quick set-ups and imports, never to your own changes

Running it day to day

• Scheduled zone backups on by default, every 24 hours, keeping the newest ten per zone, plus on-demand backups of one zone or all of them
• Restore a snapshot to make the zone match it exactly, after a safety snapshot; recover a zone that was deleted by mistake with every record it had
• Health, reconcile and orphan checks run on WHMCS's own cron. An orphan is only flagged by default, and nothing is deleted at your provider unless you choose it
• An activity log of every zone and record change, with who made it, when and whether it worked
• A scoped REST API with read or write tokens, limited to the source addresses you choose, rate limited, with every write logged against the token's name

What your customers get

• Their own DNS area with records, DNSSEC, import and export, forwarding and backups, reached by sidebar links, tabs or both
• The same validating editor you use, limited to the zones that are theirs. Another account's zone cannot be reached, even by guessing an ID
• Quick set-ups for Google Workspace, Microsoft 365 or an SPF lockdown, which add only what is missing and never a second SPF record
• Self-service backups with a five-minute pause between snapshots, downloadable as zone files
• DNSSEC status and DS records to paste at their registrar, on providers that support it

Pages render natively on WHMCS's Six, Twenty-One and Nexus themes, every string is translatable and your wording overrides survive updates.

Security built in

• Provider credentials are stored encrypted in your WHMCS database and never shown back in the form.
• Credentials never reach a customer's page, and customers never see which provider serves their DNS.

One product, every feature

PD DNS Manager is one paid module with every feature included and no per-zone, per-seat or per-record fee. Your providers bill you directly. It activates from your PD Modules subscription with no key to paste, adds its own tables and modifies no WHMCS files, and uninstalls without leaving orphans.

If your subscription lapses, your DNS records are never touched and your providers keep serving every zone. Admin management locks first while customers keep their self-service, and customer management stops later behind a neutral "temporarily unavailable" message. Renewing restores everything.

Requirements

• WHMCS 9 or later on PHP 8.2 or later, with the ionCube Loader
• An account with at least one supported DNS provider
• PD Modules, the free control panel every PD module installs into