Use record-set templates for repeatable ordinary DNS configurations. A template adds its records to a chosen zone; editing a template later does not automatically update every zone where it was previously applied.

Build a deliberate preset

1. Open cPanel DNS → Templates and create a named template.
2. Add a description explaining the intended use.
3. Save it, then add its records through the type-aware editor.
4. Review each name, type, value and TTL.
5. Keep customer-specific verification tokens and selectors out of shared presets.

Use only merge fields offered by the module and confirm the required domain/service data exists. A reusable preset should not carry a real customer’s account values into another zone.

Apply to one reviewed zone

Open the intended zone’s template action, choose the preset and review the target before confirming Apply template. Inspect the actual resulting records and any reported skips or errors.

Existing matching records are skipped. Applying a template does not promise to replace different live values or remove records absent from the preset. DNS record-set consistency and single-CNAME restrictions still apply, so read back the whole affected set.

Check the outcome before repeating

If only some records were added, inspect the result before applying again. Missing merge data, conflicting records, package limits and provider failures need different corrections.

Keep a snapshot before broader changes. Verify authoritative answers and the affected service after the intended record configuration is present. For a reviewed BIND file rather than a reusable preset, use the import/export guide.

See the PD cPanel DNS Blesta guide for related tasks, or explore the module.