Save a reusable DNS record template for your standard hosting setup, then apply it to the intended Route 53 zone. Templates reduce repeated entry, but they still need values suitable for the domain and services you are configuring.

Prepare the preset

1. Open AWS Route 53 DNS → Templates and choose the new-template action.
2. Give it a recognisable name.
3. Add the required record types, names, TTLs and values.
4. Review any domain-dependent values and mail priorities.
5. Save, then apply it to a controlled zone before wider use.

Where a supported merge field is intended, {domain} represents the zone name. For a template MX value, the documented format puts priority before the mail hostname, such as 10 mail.{domain}. That combined template value differs from the separate priority and target fields in the normal MX editor.

Apply it to the correct zone

Find the zone under Zones, open its menu and choose Apply template. Review the provider/domain and existing records before applying the preset. Inspect the records afterwards instead of assuming every template row was useful or valid for that customer.

Matching existing records are skipped. Rows with unresolved merge fields are also skipped; other rows can fail or exceed the remaining customer record allowance. Review each result count rather than treating an overall response as proof that every row was added. This is an additive configuration task, not a promise to replace all older destinations at the same name. In particular, a changed address can leave more than one value unless you deliberately edit the intended existing record.

Verify dependencies and scope

A template does not configure a mailbox, website or registrar delegation. Customer-specific verification and tenant values should not be copied into a universal preset. Check the domain’s public authoritative answer and the services that use the new records.

Editing the template is not evidence that zones where it was applied earlier have changed. Keep a snapshot before a broad DNS revision, and reconcile records already added after a partial refusal before applying again. Retain the template name, zone and redacted result if support is needed.

Check same-named hosted zones before changes

If your AWS account contains multiple hosted zones with the same domain name, do not assume choosing a same-named row selects a particular hosted-zone ID. This module resolves zones by name. Have your AWS administrator compare the exact hosted-zone ID, records and delegated nameservers before using module writes; use AWS’s native zone-specific controls if the target remains ambiguous. Do not create or delete another zone to diagnose that ambiguity.

Check the template result

Your hosting team should compare the saved template, intended domain values and actual before/after record sets. Check the added, skipped, failed and over-allowance results separately; a skipped row may already exist or still need a domain-dependent value. A partly applied preset is not a complete replacement. Review the existing values before applying it again.

See the PD AWS Route 53 DNS WHMCS guide for related tasks, or explore the module.