volker.raschekandCopilot 3557776f17
Lint Markdown files / markdown-lint (push) Successful in 10s
Ansible Linter / ansible-lint (push) Successful in 52s
Release Ansible Role / Release Ansible Role (push) Successful in 1m19s
fix(templates): render allow-notify and correct allow-query-on statement
The zone option allow_notify was documented in defaults/main.yaml but never rendered by
named.conf.views.j2. Any allow_notify list configured for a zone was silently dropped, so
secondaries kept accepting NOTIFY messages only from the hosts listed in the masters statement.

In addition, the allow_query_on block emitted the statement name allow-query instead of
allow-query-on. This produced a second allow-query clause in the same zone and thereby
overrode the interface restriction that was actually intended.

Co-authored-by: Copilot <copilot@github.com>
2026-09-02 10:46:46 +02:00
2025-11-23 22:00:15 +01:00
2025-11-23 22:00:15 +01:00
2025-11-23 22:00:15 +01:00
2025-11-23 22:00:15 +01:00
2023-02-08 17:56:13 +01:00
2022-02-21 22:11:41 +01:00
2025-04-14 21:53:40 +02:00

bind9-role

Ansible Role

With following role can be bind installed and configured.

Installation

ansible-galaxy install volker_raschek.bind9

Supported distributions

  • Arch Linux
  • Rocky Linux 8
  • Ubuntu 20.04

Features

  • Installing bind/named
  • Configuring bind/named
    • TSIG-Keys
    • Simple Zones
    • Zones with different views
    • DYNDNS

Configuring

In the default directory are examples how to configure named. Copy the defaults into your host_vars or group_vars and adapt the examples.

Individual host-templates

Each host has his own zones templates. Store the template in templates/<hostname>/etc/named/zones/<name-of-view>/zone.conf. For example: templates/ns1.example.com/etc/named/zones/internal/db.de.example.

S
Description
Ansible role to setup named/bind
Readme MIT
185 KiB
Languages
Jinja 100%