volker.raschek/ansible-role-bind9
1
0
Fork 0
Code Issues 1 Pull Requests 1 Projects Releases Wiki Activity
Ansible role to setup named/bind
34 Commits 2 Branches 0 Tags 160 KiB
Jinja 100%
19e6e3a5a0
Go to file
CSRBot 19e6e3a5a0
All checks were successful
continuous-integration/drone/pr Build is passing
Details
continuous-integration/drone/push Build is passing
Details
chore(deps): update dependency docker.io/volkerraschek/markdownlint to v0.35.0
2023-06-17 23:00:48 +02:00
defaults feat: support rndc 2023-06-09 09:46:02 +02:00
handlers refac: adapt style to pass ansible-lint checks 2023-02-08 21:47:45 +01:00
meta fix(galaxy): meta information 2023-02-08 21:30:35 +01:00
tasks feat: support rndc 2023-06-09 09:46:02 +02:00
templates/etc feat: support rndc 2023-06-09 09:46:02 +02:00
vars fix: add linter 2023-02-08 17:56:13 +01:00
.ansible-lint fix(galaxy): meta information 2023-02-08 21:30:35 +01:00
.drone.yml chore(deps): update dependency docker.io/volkerraschek/markdownlint to v0.35.0 2023-06-17 23:00:48 +02:00
.editorconfig fix(ci): drone, markdownlint, renovate 2022-02-21 22:08:10 +01:00
.markdownlint.yaml fix(galaxy): meta information 2023-02-08 21:30:35 +01:00
.yamllint.yaml fix: add linter 2023-02-08 17:56:13 +01:00
LICENSE fix: add license 2022-02-21 22:11:41 +01:00
README.md fix(ci): replace git repository with gitea instead of drone 2022-04-27 20:13:27 +02:00
renovate.json fix(ci): drone, markdownlint, renovate 2022-02-21 22:08:10 +01:00

README.md

bind9-role

Build Status 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.