DNS Templates
Clone, edit and delete Eenos v2 DNS templates while understanding scope precedence and existing-zone effects.
Open Network & DNS → DNS → DNS Templates.
Scopes and precedence
| Scope | Owner | Available actions |
|---|---|---|
| Global | root; supplied templates | Clone globally or for an account. |
| Global Custom | root | Clone, edit and delete. |
| User Custom | Named account | Clone, edit and delete. |
The table displays Name, Scope, Owner and Actions. Templates are resolved by name in this order: account custom → global custom → supplied global, within the zone's schema version. A same-named custom template can therefore override a broader definition for its consumers.
Clone a template
- Find the source row.
- Choose Clone globally or Clone for account.
- Enter the new template name.
- For an account clone, select the existing hosting account.
- Click Clone Template and check the result.
Names allow letters, numbers, dots, underscores and hyphens, with a maximum of 200 characters. Global clone validation rejects names beginning or ending with dot, hyphen or underscore, and rejects an existing global custom destination. Account clones reject an existing destination for that account.
Use a name beginning and ending with a letter or digit so it also satisfies the stricter Add DNS Zone template-name validation. Do not overwrite a supplied template to customize it; clone it.
Edit a custom template
- Click Edit template on a custom row.
- Review its name and path.
- Edit Template content in the code editor.
- Click Save Template, review the confirmation and confirm the save.
- Verify generation with an intended zone before applying the template more widely.
The current editor labels the content as Mako template syntax. Preserve the structure and variables of a compatible v2 source template. The save operation requires nonempty content but does not validate a complete DNS build before writing it.
A saved template can still fail to generate DNS
Keep a copy before editing. Syntax errors or incompatible template assumptions can prevent later zone generation. Existing generated zones are not automatically rebuilt when this editor saves the template.
Delete a custom template
Click Delete template, check the named template in the confirmation and click Delete Template, or Cancel. Built-in rows do not expose edit/delete controls.
Review every zone using the name before deletion. If a broader same-named template exists, future resolution can fall back to it; otherwise later generation can fail. The delete workflow does not provide a consumer-impact preview or rebuild affected zones.
Use the template
Select it in Add DNS Zone or choose Change Template from View All DNS Zones. Review its scope for the chosen account, then verify the rendered and authoritative records.