From: Peter van Dijk Date: Tue, 1 Jul 2025 09:46:01 +0000 (+0200) Subject: document current views/catz interaction situation X-Git-Tag: rec-5.3.0-alpha2~17^2 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=b3ec1efbe3c7a3b09122291a5794e82316d315eb;p=thirdparty%2Fpdns.git document current views/catz interaction situation Signed-off-by: Peter van Dijk --- diff --git a/docs/catalog.rst b/docs/catalog.rst index e641f77a68..05d88bb2ca 100644 --- a/docs/catalog.rst +++ b/docs/catalog.rst @@ -29,6 +29,8 @@ Currently, the following backends have been modified to support catalog zones: - :doc:`godbc ` - :doc:`lmdb ` +If you are also using views, please read :ref:`views-catalog-zones` in the Views documentation. + .. _catalog-configuration-options: Configuration options diff --git a/docs/views.rst b/docs/views.rst index 0a36ad688f..45c68fbc52 100644 --- a/docs/views.rst +++ b/docs/views.rst @@ -223,3 +223,15 @@ The equivalent PowerDNS setup would be:: pdnsutil load-zone example.com..internal internal/primary.example.com pdnsutil load-zone example.com..external external/primary.example.com + +.. _views-catalog-zones: + +Interaction with catalog zones +------------------------------ + +Catalog zones (both producer and consumer) can have variant names, and contain variant member zone names. +Producer zones are looked up via views like any other zone, but on the wire contain non-variant names. +Thus, it is important to make sure that the member zones of a catalog are visible to the same consumer in the same view. + +On the consumer side, member zone names currently do not get a variant assigned to them, and thus are not automatically scoped to (a) certain view(s). +This is expected to improve in the future.