On 27/11/2019 12:59, Steven Relf wrote:

Hi list....   I'm looking at making use of Designate, and have so far managed to get designate configured and working against a single bind9 server.   The issue I'm having, and this could be due to not understanding bind config well, is how do I configure other bind servers to be slaves of the server used by designate. I keep running into an issue where the slave doesn’t want to do a transfer and errors with "received notify for zone 'domain': not authoritative" I'm assuming this has something to do with the slave not knowing about the zone.   So the question, do I have to have all my bind servers hooked upto designate, and managed with a mdns service, or am I missing something obvious.  

Yes, when using Designate and Bind, Designate (or in this case the designate-mdns server) is the "master" DNS server. As the bind nodes are configured to pull the data from Designate, they will not allow other servers to pull from them. To add this, you need to add extra "targets" in your pools.yaml file for the pool you are adding the servers to see [1] for an example. Thanks, Graham 1 - https://opendev.org/openstack/designate/src/branch/master/etc/designate/pool...

Rgds Steve.   The future has already arrived. It's just not evenly distributed yet - William Gibson