DNS Zone Templates
Customize Eenos DNS zone templates using version-aware account, global custom and default lookup paths.
DNS zone templates must match the stored zone schema. The current resolver supports version 1 and version 2; an unversioned valid legacy zone is treated as v1. DNS v2 requires explicit version: 2 with the corresponding metadata and record structures.
Lookup order
For version N and the zone's selected template name:
/var/eenos/userdata/<user>/templates/dns/vN/<template>/usr/local/eenos/templates/dns/vN/custom/<template>/usr/local/eenos/templates/dns/vN/<template>
Only v1 then falls back to the legacy account templates/dns/, global dns/custom/ and global dns/ directories. V2 does not use those unversioned fallbacks. The v1 template selector uses the legacy zonetempalte field; v2 uses metadata.template.
The resolver rejects invalid user/template path components and a selected file escaping its root. A missing compatible template raises an error; an old template is not automatically converted to the new zone data structure.
Customize and verify
Clone a default for the correct schema into the matching account or global custom directory. Preserve the variables and record handling expected by that schema. An account override affects that account's selected zones; a global override can affect many accounts.
Test rendering with representative SOA/NS and supported record types, then validate the resulting zone through the DNS tooling and managed workflow before deployment. Preserve serial/record semantics and existing zone content; do not trigger live zone regeneration or DNS changes just to preview a template.
Use WAP DNS for operational controls. The old unversioned path table is not sufficient guidance for current DNS v2 zones.