The *named* role now supports generating configuration for authoritative DNS zones and DNSSEC keys. Zones are defined by populating the `named_zones` variable with a list of objects describing the zone. Zone properties can include: * `name`: The DNS domain name * `type`: The zone type, defaults to `master` * `allow_update`: A list of hosts/networks or DNSSEC key names (which must be specified as an object with a `key` property) * `update_policy`: A list of BIND update policy statements * `ttl`: The default (minimum) TTL for the zone * `origin`: The authoritative name server for the zone * `refresh`, `retry`, `expire`: Record cache timeout values * `default_records`: A list of default records, defined as objects with the following properties: * `name`: The RR name * `type`: The RR type (default: `A`) * `value`: The RR value Zone files will be created in `/var/named/dynamic`. Existing zone files will **not** be overwritten; management of zone records is done using `nsupdate` or similar.
16 lines
619 B
Django/Jinja
16 lines
619 B
Django/Jinja
$TTL {{ item.ttl|d(named_default_ttl) }}
|
|
@ IN SOA {{ item.origin|d(ansible_fqdn + '.') }} {{ item.contact|d('hostmaster.{}.'.format(item.zone)) }} (
|
|
{{ ansible_date_time.year }}{{ ansible_date_time.month }}{{ ansible_date_time.day }}00
|
|
{{ item.refresh|d(named_default_refresh) }}
|
|
{{ item.retry|d(named_default_retry) }}
|
|
{{ item.expire|d(named_default_expire) }}
|
|
{{ item.ttl|d(named_default_ttl) }}
|
|
)
|
|
|
|
IN NS {{ item.origin|d(ansible_fqdn + '.') }}
|
|
{% if item.default_records is defined %}
|
|
{% for rr in item.default_records %}
|
|
{{ rr.name }} IN {{ rr.type|d('A') }} {{ rr.value }}
|
|
{% endfor %}
|
|
{% endif %}
|