Save a repeatable set of ordinary DNS records as a template, then apply it to the intended managed zone. Check that its destinations and mail values suit the service you are configuring for this customer.

Build a useful preset

1. Open Google Cloud DNS → Templates and choose Add template.
2. Give the preset a recognisable purpose-based name.
3. Add the intended types, names, TTLs and values.
4. Review supported merge fields and their prerequisites.
5. Save, then inspect the result in a controlled zone before broader use.

The documented {domain} field represents the zone name. {ip} depends on an available apex address; do not assume it can resolve before its prerequisite exists.

For a template MX value, the documented format puts priority before the target, such as 10 mail.{domain}. That combined value differs from the ordinary MX editor’s separate priority and target inputs.

Apply and compare the actual records

Open the intended zone’s menu and choose Apply template. Review the provider/project and existing record set before confirming. Compare the results rather than treating a success message as proof the website or mail service works.

Matching records are recognised and skipped. Rows with unresolved merge fields are also skipped; others can fail or be blocked by the remaining customer allowance. Check the added, skipped, failed and over-allowance counts individually. Additive application is not an instruction to remove every old destination at the same name. Editing a template later is not evidence that previously configured zones changed.

Keep data and scope clear

A reusable preset should not carry another customer’s verification, selector or tenant values. Google Cloud record-set restrictions still apply, including a shared TTL and a single CNAME target.

If only part of an application succeeds, inspect what was added before repeating it. A missing merge prerequisite, a quota refusal and a provider-permission failure need different corrections. Keep a record snapshot before broader changes and verify authoritative DNS plus the affected service after the intended configuration is in place.

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