PD BIND 9 DNS for WHMCS and Blesta

PD BIND 9 DNS — BIND 9 Zone & Record Management for WHMCS and Blesta

Manage your BIND 9 DNS zones and records inside WHMCS or Blesta — fast, self-service, auto-provisioned

Made and supported by Projektif Digital Ltd. Runs inside PD Modules, the panel every module installs into.

Domains & DNS

Available for WHMCS and Blesta

Full BIND 9 DNS management inside WHMCS or Blesta

If you run your own ISC BIND 9 name server, PD BIND 9 DNS brings every hosted zone and record under your WHMCS or Blesta admin — and gives your customers a clean, self-service Manage DNS portal so they can add and update their own records without opening a support ticket.

The admin panel your team actually needs

Every zone file on your BIND server appears in a fast, searchable list the moment you connect over SSH. No import. No sync. No manual setup per zone. The list pages server-side, so performance stays consistent whether you have ten zones or ten thousand.

Open any zone and you get a full record editor with live filtering by type and name. Changes write directly to the BIND zone file — there is no local cache to get out of sync.

Atomic writes — named-checkzone before every change

Every record change goes through a lock → read → mutate → SOA bump → named-checkzone → promote → rndc reload sequence. If named-checkzone rejects the change, the temporary file is discarded and the live zone file is never touched. You cannot accidentally break DNS with a typo — the module enforces it.

A type-aware editor that prevents mistakes

Choosing a record type in the editor shows exactly the right fields for that type — and only those fields. An MX record gets a priority and a mail server target; an SRV record gets all four SRV fields; a TLSA record gets the certificate fields. Built-in validators prevent a malformed record from being saved. Supports A, AAAA, CNAME, MX, TXT, NS, SRV, CAA, PTR, TLSA, SSHFP, NAPTR and more.

Customer self-service that reduces tickets

Bind any zone to a WHMCS or Blesta client and a Manage DNS link appears in their client portal — on their domain page, their service page, or in the navigation. Customers use the same type-aware editor (backed by the same atomic write sequence) to add, edit and delete their own records, without support involvement and without any access to your BIND server.

Zone backups — point-in-time, per zone, automated

Scheduled BIND-format snapshots of every zone run automatically. Restore any zone to a previous state in one click — the restore goes through named-checkzone and writes directly to your BIND server. Download any snapshot as a BIND zone file.

Auto-provision DNS on domain registration

A DNS zone is created on your BIND server automatically whenever a customer registers or transfers a domain, or orders a service. Each new zone gets a valid SOA and NS block using your configured authoritative nameservers, validated by named-checkzone and reloaded into BIND.

Connect over SSH — no new API keys, no third-party accounts

Authenticate with an SSH private key (or password). Your team works inside WHMCS or Blesta — no one needs shell access to the BIND server for day-to-day DNS work. The private key is stored encrypted in your WHMCS or Blesta database and never exposed through the module interface.

---

Feature highlights

  • Connect your BIND server once over SSH — all zone files load automatically, no import needed
  • Atomic record writes: lock → mutate → SOA bump → named-checkzone → rndc reload — a bad record never touches the live file
  • Type-aware record editor for A, AAAA, CNAME, MX, TXT, NS, SRV, CAA, PTR, TLSA, SSHFP, NAPTR with validation
  • Customer self-service "Manage DNS" portal inside the WHMCS or Blesta client area
  • Renders on all bundled WHMCS or Blesta themes — Six (Bootstrap 3), Twenty-One and Nexus (Bootstrap 4)
  • Scheduled BIND-format zone backups with configurable frequency and retention
  • One-click zone restore from any backup snapshot
  • Auto-provision DNS zones on domain registration, transfer and service setup
  • Secondary zone support — the module wires the named.conf slave block and runs rndc reconfig
  • BIND-format zone import and export
  • Record templates — save a set and apply to any zone in one click
  • Reverse DNS / PTR record management for your IP ranges
  • Background zone health and orphan checks with optional admin email alerts
  • Activity log for every zone and record operation with admin and client attribution
  • SSH private key or password authentication — stored encrypted, never exposed

---

Requirements

  • PHP 8.1 or later
  • PD Modules (PD Core) installed in your WHMCS or Blesta admin (free; the delivery platform for all PD Modules)
  • A BIND 9 server reachable over SSH from your WHMCS or Blesta server, with a user that can read and write the zone files, run rndc, and run named-checkzone

Questions

Which billing platforms does PD BIND 9 DNS work with?

PD BIND 9 DNS is available for WHMCS (8.13 or later) and Blesta (6.0 or later). Each has its own page with the screenshots, requirements and price for that system. A module is added to the PD Modules licence of the installation it runs on, so a WHMCS installation and a Blesta installation each hold their own licence.

Does PD BIND 9 DNS store my DNS records?

No. Your BIND 9 server remains the single source of truth. The module reads records live from your zone files over SSH and writes changes straight back to them. The only things kept in your WHMCS or Blesta database are metadata — zone ownership, backup snapshots and activity logs. There is no local copy of your records to drift out of sync.

What kind of BIND server and access does it need?

A running ISC BIND 9 server that is reachable over SSH from your WHMCS or Blesta server. It connects with an SSH user that can read and write your zone files and run rndc and named-checkzone. Because a non-login SSH shell often has a minimal PATH, you provide the full paths to rndc and named-checkzone so the module can always find them.

How does it connect, and is my key safe?

You connect once over SSH — no new API keys and no third-party accounts. An SSH private key is preferred (a password also works). The key is stored encrypted in your WHMCS or Blesta database, shown masked in the interface and never exposed through the module. Your team does day-to-day DNS work inside WHMCS or Blesta without anyone needing shell access to the BIND server.

How does it make sure a record change won't break my zone?

Every change is an atomic write: lock the zone, read the current file, bump the SOA serial, validate the result with named-checkzone, promote it, then run rndc reload. If named-checkzone rejects the change, it is discarded and your live zone file is never touched. A typo cannot take a zone down.

Why do I have to configure authoritative nameservers?

When the module creates a new zone, it needs valid SOA and NS records to write. Your configured authoritative nameservers become the zone's SOA MNAME and its NS records, so every new zone is served correctly by your own name servers from the moment it is created. It is a required part of setup for this reason.

Is DNSSEC supported?

No. PD BIND 9 DNS does not sign zones or manage DNSSEC keys. If you need signed zones, keep signing them with your own BIND tooling (for example dnssec-policy on your server) — the module manages your record data and leaves DNSSEC key management to BIND.

Can it manage secondary (slave) zones?

Yes. The module can add a secondary zone block to your configuration and run rndc reconfig so your BIND server starts serving the slave zone. This is handy when you run BIND as a secondary for zones that are primary elsewhere.

What happens to my zones if the subscription lapses?

Your DNS records are never touched. Zones stay exactly as they are on your BIND server and keep resolving without interruption. A lapsed subscription only withdraws admin management and customer self-service inside WHMCS or Blesta — everything resumes as soon as the subscription is renewed.

What does it cost to run, on top of the subscription?

Only what you already pay your provider. PD BIND 9 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.

Get your website online with PD Hosting

UK hosting, domains and support from a real team. From a first site to a full server.

Terms and Conditions  ·  Privacy Policy

PD Hosting is the trading name of Projektif Digital Ltd, registered in England and Wales, company number 12482555.

PD Hosting
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.