Use PD Cloudflare DNS templates to apply a repeatable set of records to customer zones. A template should contain values you intend to reuse, with zone-specific merge fields where appropriate.

Plan the record set

Decide whether the template is for hosting, mail or another defined setup. A mailbox provider’s DKIM or verification value may be account-specific and unsuitable for a general template. Check that any merge fields produce the intended names and destinations for each zone.

Create and apply a template

1. Open PD Modules → Cloudflare DNS → Templates → Add template.
2. Give it a name that describes its purpose and add the required records.
3. Use supported merge fields such as {domain} and {ip} where those values are intended.
4. For a template MX value, enter priority before the mail host, for example 10 mail.{domain}, as required by the template format.
5. Save the template, then review the target zone’s existing records and take an appropriate backup.
6. Open that zone’s ⋯ → Apply template and choose the intended template.
7. Review the resulting records and resolved merge-field values.

Existing matching records are skipped. Applying a template is additive; it is not a full reconciliation that removes obsolete records or overwrites every conflicting value.

Verify the intended outcome

Check hostnames, addresses, mail priorities and any provider-specific values in the final zone. A completed apply operation does not prove a web or mail service is configured at the other end.

Do not treat applying the same template again as a way to update values already in the zone. Inspect what exists, then edit deliberately when a record needs a different target.

Change a template carefully

Editing a template prepares future applications. Do not assume all zones previously using it have changed automatically. Identify the zones needing a reviewed change and preserve their customer-specific records.

If a template apply partly fails, inspect the records added before repeating it. Your hosting team should retain the template name, target zone, original action time and exact redacted error while checking which changes completed. Use backups and restore when you need a recovery point, and distinguish a restore’s replacement effect from template application.

Check the template result

Your hosting team should compare the selected template and target zone with the original added, skipped, failed and allowance-blocked results. Inspect resolved names, destinations and existing records before another apply. An unresolved merge field can be skipped, and a changed template does not update zones already using it. Do not delete customer-specific records or use a snapshot restore merely to force an additive template to match.

See the PD Cloudflare DNS WHMCS guide for related tasks, or explore the module.