
Introduce an NS1 backend. Signed-off-by: Michael Hood <mhood@ns1.com> Change-Id: I80fe08238005a94161e2dbcc89e77c90cde0a715
2.0 KiB
2.0 KiB
NS1 Backend
NS1 Configuration
- Configure the NS1 Backend using this sample target snippet
sample_yaml_snippets/ns1.yaml
- Then update the pools in designate
$ designate-manage pool update
See designate_manage_pool
for further details on the
designate-manage pool
command, and pools
for information about
the yaml file syntax
TSIG Key Configuration
In some cases a deployer may need to use tsig keys to sign AXFR (zone transfer) requests. As NS1 does not support a per host key setup, this needs to be set on a per zone basis, on creation.
To do this, generate a tsigkey using any of available utilities (e.g. tsig-keygen):
$ tsig-keygen -a hmac-sha512 testkey
key "testkey" {
algorithm hmac-sha512;
secret "vQbMI3u5QGUyRu6FWRm16eL0F0dfOOmVJjWKCTg4mIMNnba0g2PLrV+0G92WcTfJrgqZ20a4hv3RWDICKCcJhw==";
};
Then insert it into Designate. Make sure the pool id is correct (the
--resource-id
below.)
openstack tsigkey create --name testkey --algorithm hmac-sha512 --secret 4EJz00m4ZWe005HjLiXRedJbSnCUx5Dt+4wVYsBweG5HKAV6cqSVJ/oem/6mLgDNFAlLP3Jg0npbg1SkP7RMDg== --scope POOL --resource-id 794ccc2c-d751-44fe-b57f-8894c9f5c842
Then add it to the pools.yaml
file as shown in the
example.