
The pool-manager has been deprecated since Newton and is now being removed with the Train release. Change-Id: Ib258043d492bb25e1c061d765b40885317c73804
1.8 KiB
Bind9 Backend
This page documents using the 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 Designate (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
Bind9 Configuration
Ensure Bind can access the /etc/bind/rndc.conf and /etc/bind/rndc.key files and receive rndc traffic from Designate.
Enable rndc addzone/delzone functionality by editing named.conf.options or named.conf and add this line under options
-new-zones yes; allow
Example configuration of /etc/bind/rndc.key
"rndc-key" {
key -md5;
algorithm hmac"<b64-encoded string>";
secret };