PD Azure DNS — Microsoft Azure Zone & Record Management for WHMCS
Manage your Azure 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 & DNS
Connect your Azure subscription once and every DNS zone loads automatically — one Cloud Shell command creates the credentials, with an instant connection test and secret-expiry warnings before anything breaks.Every Azure DNS zone in one searchable list — filter by provider or client, see nameservers, sync and backup status at a glance, and jump straight to records. Scales to hundreds of zones.Live zone records managed without leaving WHMCS — colour-coded type badges for A, AAAA, MX, TXT, SRV, CAA and more, with inline edit from every row. Changes write to Azure DNS immediately.Type-aware record editor shows Priority and Mail server the moment you pick MX — every record type gets exactly the right fields with built-in validation to prevent a bad record going live.DNSSEC in two clicks — sign a zone and the DS record, keytag, algorithm and digest your registrar needs are surfaced immediately, ready to copy across, no manual key wrangling.Scheduled BIND-format zone backups with configurable retention — every zone snapshotted automatically, on-demand backups whenever you need one, and one-click restore if a change goes wrong.Customers manage their own Azure DNS inside the WHMCS client portal — zone list with status badges and a direct Manage records link, no support ticket needed. Shown on Six (BS3).Full DNS record editor in the client area — customers add and edit any record type with the same type-aware form admins use, backed by Azure DNS in real time. Twenty-One (BS4).1 / 8
PD Azure DNS lets a hosting company run customer DNS on Microsoft Azure DNS and manage all of it from WHMCS. Connect your Azure subscription once and every hosted zone appears in your admin area with no import, and your customers edit their own records from your client area without an Azure login or a support ticket.
It is built for hosts and agencies who keep their zones in Azure DNS and want their team and their customers working from WHMCS, not from the Azure portal.
Why hosts choose PD Azure DNS
Connect in minutes, with help when it goes wrong. One Azure Cloud Shell command creates the access credentials the provider form needs. When a value is wrong, Test connection tells you which one and what to fix, instead of a generic failure.
No expired-secret surprises. Enter the expiry date of your Azure secret and Test connection counts down to it, with warnings 60, 30 and 7 days before it runs out, so DNS changes do not fail the day it lapses.
Delegation is never missed. A zone's Azure name servers are shown right on the Zones list, so you can see at a glance what a domain must point to at its registrar.
DNSSEC without the key handling. Sign a zone with one button and the DS record and key details your registrar asks for are shown, ready to copy.
Customers help themselves. Customers manage their own records and snapshots with no access to your Azure subscription.
How it works
Connect Azure. Run the single Cloud Shell command Azure DNS gives you, paste the values into the provider form and press Test connection. Enter the secret's expiry date to get the warnings.
Your zones appear. Every zone in the subscription is listed with its Azure name servers, health, sync and DNSSEC state. Assign each to a client, or let Track matched zones do it.
Turn on what you sell. Create templates and packages, link packages to your products, and switch on auto-provisioning if you want a zone created whenever a domain is registered or a service is set up.
Customers manage their own DNS. They add records, switch on DNSSEC and restore from snapshots, and you see every change in Activity.
What you get in WHMCS
Connecting and zones
Add Azure DNS from Providers; one Azure Cloud Shell command creates the credentials the form needs
Test connection names the value that is wrong and what to fix; with the secret's expiry date entered, it counts down and warns 60, 30 and 7 days ahead
More than one Azure account can be connected and managed in the same interface
A zone's Azure name servers are shown on the Zones list
Every zone is listed with no import or sync step, read live from Azure DNS; changes are written straight back and the module keeps no copy of your records
Server-side paging, search and sort keep the list fast with thousands of zones; narrow it by name, provider, status or client
Track matched zones binds every zone matching an active domain or service to its client in one step, changing nothing at the provider
Lock a zone against the client's own changes; admins keep full control and the client keeps read access
Records
A type-aware editor that shows only the fields the type uses: priority and mail server for MX, priority, weight, port and target for SRV, flags, tag and value for CAA
Addresses and hostnames are checked before saving, so a malformed record never reaches the provider. Search by name or value and filter by type
Export a zone as a BIND zone file. Import adds only missing records and shows how many before it writes anything
DNSSEC per zone with one button on the Records page: when it is on, the DS record and key details (keytag, algorithm, digest type and digest) are shown copy-ready for the registrar
Selling DNS with your WHMCS products
Zone allowances: a DNS package caps how many zones a customer may have and is linked to your WHMCS products; the largest allowance wins
Record limits per zone and per record type, held in the customer's editor, imports, templates and the API
Templates: apply a named set of records to any zone in one click, with merge fields such as {domain}, {ns1} and {ip}; applying twice is safe
Auto-provision, off until you switch it on: a zone is created and bound to the client when a domain is registered, transferred or set up with a service. A failure is logged and never interrupts the order
TLD takeover: for the extensions you choose, a newly registered or transferred domain also gets its nameservers pointed at Azure DNS
Running it day to day
Backups on by default: every zone is snapshotted as a BIND zone file each 24 hours, keeping the newest 10, with settings for both and an optional age cap. Back up one zone or all on demand
Restore makes a zone match a snapshot exactly, after a safety snapshot; a zone deleted by mistake is recovered with every record
Optional emails, off until you turn them on: admin alerts for drift or a failed backup, and customer notices when a zone is created, removed or changed by staff
A REST API with named read or write tokens and optional source-IP limits. Tokens are shown once and stored hashed, and writes pass the same checks as the panel. Every API write is logged in Activity
In your client area
A Manage DNS link on a client's domain and service pages whenever that domain or service has a zone, plus a navigation link whose text and place you choose
The link can replace the registrar's DNS Management link, sit beside it, or be left out; a zone's pages use sidebar links, tabs, or either alone
What your customers get
Their own zones, and only theirs. A customer sees and changes only zones bound to their account. This is enforced on the server, not just hidden in the page
The same editor your team uses. Add, edit and delete records in their own zones with the validating, type-aware form, written straight to the provider
Snapshots they control. With client backups on, customers snapshot their zone, download any snapshot and restore one, with a safety snapshot first. Turn it off to keep backups admin-only
One-click set-ups. Quick set-ups add the records Google Workspace or Microsoft 365 needs, or an SPF lockdown, without changing anything already there
Read-only where you say so. A locked zone is view-only, and for a domain with no hosting here you choose full editing, view only or hidden
DNSSEC for their own zone. A customer can turn DNSSEC on or off and copy the DS record, except on a zone you have locked or a domain-only zone you set to view only or hidden
The customer's Manage DNS page in your client area: their zones, each with a Manage records buttonThe customer's record editor, with DNSSEC and zone file import and export
Pages render natively on WHMCS's Six, Twenty-One and Nexus themes and are fully translatable, with wording overrides that survive updates.
Security built in
Azure credentials are stored encrypted, with tamper-evident encryption, in your WHMCS database and are never shown back in the provider form.
The stored credential is used only to read and update zones and records in the connected account.
Credentials never reach a customer-facing page, and customers' DNS pages and emails never name the backend that serves their DNS.
To rotate a credential, edit the provider, enter the new one, test and save. The old one can then be revoked with nothing else to change.
Content policy: blocked patterns and IP allow and deny lists refuse matching customer saves; admin changes are never restricted
One product, every feature
PD Azure DNS is one paid module with everything included: zones, records, backups, templates, packages, auto-provisioning, the API and customer self-service. There are no add-on tiers to compare, and beyond the subscription there is no per-zone, per-seat or per-unit fee. It installs into PD Modules in one click, adds its own tables and templates, modifies no WHMCS files, and removes everything on uninstall.
Your customers are not cut off if your subscription lapses. DNS records are never touched and the provider keeps serving your zones. Admin management locks first while customers keep their own self-service; customer management stops later behind a neutral "temporarily unavailable" message, and renewing restores everything.
Requirements
WHMCS 9 or later on PHP 8.2 or later, with the ionCube Loader
An Azure subscription to hold your DNS zones
PD Modules, the free control panel every PD module installs into
Questions
Does PD Azure DNS store my DNS records?
No. Every change writes directly to Azure DNS through its API — there is no local copy of your records to get out of sync or to lose.
What do I need to connect Azure DNS?
An Azure service-principal credential with permission to manage DNS zones in your subscription. You connect it once and every zone loads automatically.
Does removing a zone in WHMCS delete it from Azure DNS?
No. Unbinding a zone in WHMCS only removes it from the module's view — the zone and its records stay in Azure DNS untouched.
What record types are supported?
A, AAAA, CNAME, MX, TXT, SRV, CAA and NS, each with a type-aware editor that checks addresses and hostnames before saving.
What happens to my zones if my subscription lapses?
Your zones keep resolving — they live in Azure DNS, not in the module. Management is withdrawn until the account is brought back into good standing; nothing is deleted.
Can customers manage their own DNS?
Yes. Bind a zone to a client and a Manage DNS link appears in their portal, giving them the same type-aware editor for their own records — with no access to your Azure subscription.
What happens if my subscription lapses?
Nothing of yours is touched, and nothing is deleted. The module steps down in stages instead: a 14-day grace period where everything still works and you get a renewal reminder, then admin management locks while your customers carry on being served, and only after that do the customer-facing features stop — behind a neutral "temporarily unavailable, please contact support" message that never mentions licensing to your customer. Anything the module provisioned keeps running in your own account throughout, and your data and settings stay exactly where they are. Renewing restores everything immediately.
What does it cost to run, on top of the subscription?
Only what you already pay your provider. PD Azure 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.
What data leaves my server?
Your customers' data stays in your WHMCS. To confirm your licence, the platform sends us four things and nothing else: your licence key, the domain, your server's own IP address and the directory it is installed in — the four values recorded against your licence in your client area. Alongside that we see which module and version you run and whether its licence is healthy, so we can ship compatible updates. We never receive your clients' personal data, your credentials, or the contents of your WHMCS. Crash reports are off unless you turn them on, and a diagnostic report is only ever sent when you send one, after showing you a preview you can edit.
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.
Featured
