From: Pieter Lexis <pieter.lexis@powerdns.com>
Date: Mon, 13 Jun 2016 15:59:54 +0000 (+0200)
Subject: Add note on domain metadata and backends
X-Git-Tag: auth-4.0.0-rc1~45^2~4
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=cdc3cad1fb1f18a6278468ae15a76d8ac2f262c2;p=thirdparty%2Fpdns.git

Add note on domain metadata and backends

Closes #568
---

diff --git a/docs/markdown/authoritative/domainmetadata.md b/docs/markdown/authoritative/domainmetadata.md
index 5403fd3640..84e97d29b7 100644
--- a/docs/markdown/authoritative/domainmetadata.md
+++ b/docs/markdown/authoritative/domainmetadata.md
@@ -1,11 +1,17 @@
 # Per zone settings aka Domain Metadata
-Starting with the PowerDNS Authoritative Server 3.0, each served zone can have
-"metadata". Such metadata determines how this zone behaves in certain circumstances.
+Each served zone can have "metadata". Such metadata determines how this zone
+behaves in certain circumstances.
 
 **Warning**: Domain metadata is only available for DNSSEC capable backends! Make
 sure to enable the proper '-dnssec' setting to benefit, and to have performed
 the DNSSEC schema update.
 
+For the BIND backend, this information is either stored in the
+[`bind-dnssec-db`](backend-bind.md) or the hybrid database, depending on your
+settings.
+
+For the implementation in non-sql backends, please review your backend's documentation.
+
 ## ALLOW-AXFR-FROM
 Starting with the PowerDNS Authoritative Server 3.1, per-zone AXFR ACLs can be
 stored in the domainmetadata table.