PD AWS Route 53 DNS for WHMCS
£12/mo or £120 annual (save £24)
- Requires
- WHMCS 8.13 or later
- Version
- 0.1.102
- Updated
- 31 Oct 2026
Manage your AWS Route 53 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.
£12/mo or £120 annual (save £24)
£12/mo or £120 annual (save £24)
If your infrastructure runs on Route 53 nameservers, PD AWS Route 53 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.
Connect your AWS account once with an access key and every hosted zone appears immediately — 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 Route 53 over the AWS API — there is no local cache to get out of sync.
Supports A, AAAA, CNAME, MX, TXT, NS, SRV, CAA, PTR and more.
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 to add, edit and delete their own records, without support involvement and without any access to your AWS account.
The link and wording are configurable; the page renders on all bundled WHMCS or Blesta themes.
Scheduled BIND-format snapshots of every zone run automatically. Set how often they run, how many to keep per zone, and an optional age cap. Restore any zone to a previous state in one click. Download any snapshot as a standard BIND zone file. Take an on-demand backup before bulk changes.
Turn on auto-provisioning and a hosted zone is created in Route 53 automatically whenever a customer registers or transfers a domain, or orders a service. Restrict it to specific TLDs with the per-provider TLD takeover list. Failures are logged and never interrupt registration or provisioning.
---
PD AWS Route 53 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.
No. PD AWS Route 53 DNS reads records live from Route 53 and writes changes back immediately. Route 53 remains the authoritative source of truth. The module stores only metadata — zone ownership, backup snapshots and activity logs — in your WHMCS or Blesta database.
An IAM access key scoped to Route 53 with read and write access to your hosted zones — enough to list zones, read record sets, and submit record changes. You can attach an AWS-managed Route 53 policy or a tightly scoped custom policy limited to the hosted zones you want to manage.
Add an IAM access key — the Access Key ID and Secret Access Key — in the Providers panel. You can optionally set a region (Route 53 is a global service, so the region only signs the requests; it defaults to us-east-1) and an optional session token if you use temporary STS credentials. Credentials are stored encrypted and shown masked.
DNSSEC management is not offered for Route 53 in this module. If you need DNSSEC signing on a hosted zone, manage it directly in the AWS console. Everything else — records, backups, self-service and auto-provisioning — is fully managed here.