Re: [knot-dns-users] Catalog zone configuration/zone auto configuration bootstrapping

Hi Frank, yes, we need to clarify some misunderstandings. First of all, generating/updating catalog zone according to primary server configuration (that means: you change configuration e.g. by 'knotc conf-set', and the catalog zone would be updated automatically), is not implemented yet in Knot DNS 3.0. This will be 'catalog-role:generate' in some of the future versions. For now, you can only create and update the catalog zone by yourself, probably by similar means as you are used to create/update the primary server's configuration file. I can see that you, at the primary server, configured the zone dom-siew9tho.invalid. by both configuration file and catalog zone, creating a conflict. Probably Knot warned you about this in the log. The expected usage of current implementation of catalog zone is that, you put the list of member zones only in the catalog zone, and not mention them in neither primary's nor secondary's configuration file. Both servers will interpret the same catalog zone. Just configure the templates carefully, so that the primary will be a "master" for the member zones, and the secondary a "slave". I hope I made it somewhat clearer, Mit herzlichen Grüßen, Libor Dne 01.10.20 v 10:53 Frank Matthieß napsal(a):