[knot-dns-users] Re: Catalog zones when secondary to other servers

Thanks. I indeed asked a question that's half PowerDNS and half Knot. It does look like PowerDNS lets you set group info on producer zones (not consumer, which knot is doing): * https://doc.powerdns.com/authoritative/catalog.html So it sounds like I would have to do that when setting up a zone, map a bunch of things. It sounds like I would have to define the group data (Primary IP, etc) on Knot itsself, and not inherit this data via Catalog Zones? I see that catalog zones have "custom extensions" but PowerDNS doesnt support it (per link above). It may just be simpler to call PowerDNS API and create a knot config of all secondaries, which is fairly straightforward - but again completely removes the need for catalog zones in my case. I would then have: 1) zones of type Primary are using catalog 2) zones of type Secondary are using $myscript From our provisioning perspective, at least it would all done the same way - I would just have to determine more details with option 2 - like how frequent to run, how to reload knot when done, etc. Is this generally how others are doing this? Or are people only really using Catalog zones for primaries, never secondaries? Cheers, --Chris