Bind9 Backend

This page documents using the Pool Manager Bind 9 backend. The backend uses the rndc utility to create and delete zones remotely.

The traffic between rndc and Bind is authenticated with a key.

Designate Configuration

Example configuration required for Bind9 operation. One section for each pool target

sample_yaml_snippets/bind.yaml

The key and config files are relative to the host running Pool Manager (and can be different from the hosts running Bind)

Then update the pools in designate - see designate_manage_pool for further details on the designate-manage pool command

$ designate-manage pool update

Ensure Bind can access the /etc/bind/rndc.conf and /etc/bind/rndc.key files and receive rndc traffic from Pool Manager.

Enable rndc addzone/delzone functionality by editing named.conf.options or named.conf and add this line under options

allow-new-zones yes;

Example configuration of /etc/bind/rndc.key

key "rndc-key" {
    algorithm hmac-md5;
    secret "<b64-encoded string>";
};