Open Stack

Hello again,

On 01/07/2022 09:10, Christian Rohmann wrote:
> On 07/06/2022 02:04, Michael Johnson wrote:
>> There are two ways zones can be resynced:
>> 1. Using the "designate-manage pool update" command. This will force
>> an update/recreate of all of the zones.
>> [...]
> When playing with this issue of a cold start with no zones and 
> "designate-manage pool update" no fixing it.
> We found that somebody just ran into the issue of 
> (https://bugs.launchpad.net/designate/+bug/1958409/)
> and proposed a fix (rndc modzone -> rndc addzone).
>
> With this patch the "pool update" does cause all them missing zones to 
> be created in a BIND instance that has either lost it's zones
> or has just been added to the pool.


yet another update on this "cold start" and "resync" of secondary 
nameserver topic:

Since we really did not like the scaling of calling "rndc modzone" and  
"rndc addzone" for each and every zone of a pool and for every pool 
member we looked around for other solutions.
We then ran into Catalog Zones 
(https://datatracker.ietf.org/doc/draft-ietf-dnsop-dns-catalog-zones/), 
supported by major DNS servers (BIND, NSD, Knot, PowerDNS, ...), which 
can provide
just a list of zones to secondaries for their kind consideration and 
they shall then provision themselves.

Shameless pointer to the spec I proposed to add support for catalog 
zones to Designate: 
https://review.opendev.org/c/openstack/designate-specs/+/849109


Regards


Christian