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

Thanks for the draft link - glad folks realize this issue. Correct on how Primaries are stored. If we have a customer we're secondary to, we add the zone and the primary IP's they tell us (we add all zones ourselves). Some have one zone and one primary. Some have 30 zones but some zones have primary A and some have primary B. Anyhow, I created a proof of concept script that will create Knot secondary config from PowerDNS - note this isn't tested but seems about right. * https://gist.github.com/falz/b0f07945b5196a585d0fb1462467a8ea Since the primary IPs vary, I had it create a 1:1 mapping of "remote:" to "zone:". example output: #################################### # zone: customera.com # account: customera # dnssec: False remote: - id: customera.com_primary address: [10.227.254.23] zone: - domain: customera.com master: customera.com_primary #################################### # zone: mailer2.customerb.edu # account: customerbuniv # dnssec: False remote: - id: mailer2.customerb.edu_primary address: [10.44.124.10] zone: - domain: mailer2.customerb.edu master: mailer2.customerb.edu_primary ... I may or may not go this route, still exploring options. --Chris