GitLab

Catalog zones for more sophisticated provisioning, such as more about server infrastructure, not just the zones themselves.

This is a feature request for a super-catalog-zone that incorporates more server-level provisioning information and which includes the definition of views, within which, catalog zones are also defined, which once set-up, then themselves define the next layer.

We had another similar request along these lines, for propagating ACLS to slaves.

From Support ticket #11055:

---

Catalog zones allows you to automatically provision secondary zones from the master zone. Formerly we had to write scripts to translate the primary zone statements to secondary zone statements on the slave to add zones, but now catalog zones let us do that. There are view statements that may need to be added to when the service expands and that view needs more attributes or even more views

Show quoted text secZone 1 {} secZone 2 {} secZone 3 {} }

I was asking if there was a high level thing (catalog_views?) that will enable that to be automated, or do we need to write scripts to add/update/delete view level statements on the secondary servers. If we need to write scripts and we have some DNS servers that have many and varying views, the usefulness of the catalog zone for secondary zone becomes less - we still need to update all the secondary servers with view stuff.