document current views/catz interaction situation

Signed-off-by: Peter van Dijk <peter.van.dijk@powerdns.com>

diff --git a/docs/catalog.rst b/docs/catalog.rst
index e641f77a687ff0ba7de8c3978cd711dc37db6a61..05d88bb2cabb99e6cbc2f1f1d37911577057bdbc 100644 (file)
--- 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 <backends/generic-odbc>`
 - :doc:`lmdb <backends/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 0a36ad688f2ca5cb6875c0b879406333ab5e3345..45c68fbc5282d1fa5c91548e74f10b4e6d3b638c 100644 (file)
--- 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.