> Interesting. I ended up just removing the TXT record but it is unclear > why the zone entries would use that tsig labeled one instead of the > globals since they were not referencing the tsig custom properties. The labeled primaries have similar weight as the unlabled ones, and it's an entry validation error - named tries to generate a secondary zone configuration for the new entry based on the global configuration defined in the catalog zone's custom properties (sine there is no overriding configuration defined in the entry zone itself), and when reaching a labeled primary server in the list, which has no corresponding IP address record, the whole entry processing operation fails. The example configuration in ARM[1] provides a valid case with both the TSIG key and an IP address, but if you think that it is unclear, then please open a Gitlab[2] issue, and we can try to improve the documentation. > Thanks for the pointer, I'm up and running. That's good to hear, and thanks for the update. [1] https://bind9.readthedocs.io/en/v9.18.14/chapter6.html#catalog-zone-custom-properties [2] https://gitlab.isc.org/
Aram -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
