An Ansible role to configure a multi-machine BIND cluster for multiple domains.

This role will:

• install bind packages
• install more bind packages if you intend to run bind in a chroot
• template named.conf on each node
• validate locally each forward and reverse zone file before copying them on each node
• start and enable the service

Only RHEL or CentOS 6/7

The required filter_plugin to generate a reverse zone for could be embedded in ansible 2.0. Meanwhile, you will need a copy of the filter_plugins directory inside the playbook_dir or wherever you point it inside ansible.cfg

NOTE:

Default variables:

bind_packages:
  - bind.x86_64
  - bind-utils.x86_64

# do not update bind to latest unless explictly stated
bind_pkg_state: installed

# bind is not installed in a chroot and selinux is used as recommendend
# force to true if needed
bind_chroot: false
bind_service: named

# recursion is turned off
bind_options_recursion: no

# default logging channel provided in package
bind_logging_channels:
  - channel_name: default_debug
    file: 'data/named.run'
    severity: dynamic

None.

See the vagrant setup inside the test directory.

A simple playbook may look like this

- hosts: bind_cluster
  become: true
    roles:
        - bind

See configuration example in tests/group_vars/*

tests/group_vars
├── bind_cluster
├── bindmasters
└── bindslaves

In the tests directory there is:

• A group_vars directory to configure the cluster
• A Vagrantfile that will spin a cluster of 3 VM.
• A test.yml play that targets the bind_cluster groups

Hostname | ip | group |
        | :--- | :--- |
bind-m1 | 192.168.56.53 | bindmasters |
bind-m2 | 192.168.56.54 | bindslaves |
bind-m3 | 192.168.56.55 | bindslaves |

Then bind_cluster group is a child group of bindslaves and bindslaves. All three machines will be provisionned in parallel.

Those IP addresses are in the default VirtualBox Host Only network interface (192.168.56.0/24) subnet.

You can query them from your host. Install vagrant-hostmanager plugin to populate /etc/hosts of your host machine and query them via their hostname.

$ dig @192.168.56.54 machine1.example.org

PR welcome!

• template named.soa
• activate selinux when not running inside chroot
• A python script to parse all forward zones and generate all the reverse RR from them