PD Google Cloud DNS — Google Cloud Zone & Record Management for WHMCS
Manage your Google Cloud 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
Live zone records managed without leaving WHMCS — colour-coded type badges, search and filter, inline edit from every row. Changes write to Google Cloud DNS immediately.Customers manage their own 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 Google Cloud DNS in real time. Twenty-One (BS4).1 / 3
PD Google Cloud DNS lets a hosting company manage Google Cloud DNS from inside WHMCS. Connect a Google Cloud project once and every managed zone in it appears in your admin area with no import. Your customers edit their own records from your client area, and nobody on your team needs a Cloud Console login for day-to-day DNS.
It is built for hosts and agencies who keep zones in Google Cloud DNS and want to stop sharing console access, answering record-change tickets and copying zone files by hand.
Why hosts choose PD Google Cloud DNS
One service account, no console access to hand out. The provider connects with a service-account JSON key and a project that has the DNS Administrator role. Your staff and customers work in WHMCS, not in the Google Cloud Console.
Every project zone, immediately. Zones already in the project are listed the moment you connect, with no import or sync step. The list pages on the server, so it stays quick with hundreds or thousands of zones.
Records live in Google, not in a copy. Reads and writes go to Google Cloud DNS directly, so there is no local cache to drift out of date.
Customers help themselves. Customers add, edit and delete their own records, take and restore snapshots and set up Google Workspace in one click.
Provisioning that follows your orders. Switch on auto-provisioning and a zone is created in your project whenever a domain is registered or transferred, or a service with a domain is set up.
A safety net for every zone. Scheduled BIND-format snapshots run in the background, a restore is one click, and every restore takes a safety snapshot first.
How it works
Create the service account. In your Google Cloud project, create a service account with the DNS Administrator role and a JSON key.
Add the provider. Enter the project and the key in Providers and press Test connection. Your zones appear straight away.
Link zones to clients. Assign zones with the client picker, or press Track matched zones to bind every zone that matches an active domain or service.
Sell and support it. Link DNS packages to your WHMCS products to set zone allowances, switch on auto-provisioning, and let customers manage their own records.
What you get in WHMCS
Connecting and zones
Add Google Cloud DNS from Providers with a service-account JSON key and the project, which needs the DNS Administrator role
Test connection says whether the module can reach the project, and what to fix when it cannot
More than one Google Cloud account or project can be connected and managed in the same interface
Every zone is listed with no import or sync step, read live from Google Cloud 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
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 Google Cloud 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
The customer's Manage DNS page in your client area: their zones, each with a Manage records button
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
The service-account key is stored encrypted, with tamper-evident encryption, in your WHMCS database and is never shown back in the provider form.
The stored credential is used only to read and update zones and records in the connected project.
Credentials never reach a customer-facing page, and customers' DNS pages and emails never name the backend that serves their DNS.
To rotate a key, edit the provider, enter the new one, test and save. The old key 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 Google Cloud 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. This module does not sign zones or manage DNSSEC keys, and offers no DNSSEC control.
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
A Google Cloud project with Cloud DNS, and a service account with the DNS Administrator role
PD Modules, the free control panel every PD module installs into
Questions
Does PD Google Cloud DNS store my DNS records?
No. PD Google Cloud DNS reads and writes records live through the Google Cloud DNS API, applying each change as a whole-rrset transaction. Google Cloud DNS remains the authoritative source of truth — there is no local cache to get out of sync. The module stores only metadata — zone ownership, backup snapshots and activity logs — in your WHMCS database.
What do I need to connect Google Cloud DNS?
A Google Cloud project with the Cloud DNS API enabled, and a service account with the DNS Administrator role (roles/dns.admin). You paste the full service-account key JSON when adding the provider; it is stored encrypted and masked. Your team then works entirely inside WHMCS — no one needs day-to-day access to the Google Cloud Console.
Can I connect more than one Google Cloud project or account?
Yes. Add multiple providers in the Providers panel — one per GCP project or service account. You can manage the managed zones from all of them through the same interface.
Does removing a zone in WHMCS delete it from Google Cloud DNS?
Yes, if you delete it: Delete zone in a zone's ⋯ menu deletes the managed zone and all its records in Google Cloud DNS, after you confirm. Nothing else deletes a zone there unless you choose it: removing a provider, cleaning up an orphan and terminating a service all leave the zone in place, unless you turn on 'When cleaning an orphan, also delete the zone at the provider' or turn off 'Keep the DNS zone when a service is terminated'.
What record types are supported?
A, AAAA, CNAME, MX, TXT, NS, SOA, SRV, CAA, PTR, NAPTR, SSHFP, TLSA and DS, each with a type-aware editor that checks addresses and hostnames before saving.
Is DNSSEC supported?
No. PD Google Cloud DNS does not manage DNSSEC. If you need DNSSEC on a zone, enable and manage it on the managed zone directly in the Google Cloud Console; the module leaves that configuration untouched.
What happens to my 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?
Yes. Enable 'Automatically create a DNS zone on registration and new services' in Settings. A zone is created when a domain is registered or transferred, or a service with a domain is set up. Separately, the TLD takeover list on your provider names the extensions whose nameservers are also pointed at Google Cloud DNS 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 Google Cloud 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.
Featured
