From: Peter van Dijk <peter.van.dijk@powerdns.com>
Date: Tue, 3 May 2016 11:14:12 +0000 (+0200)
Subject: document outgoing-axfr-expand-alias
X-Git-Tag: rec-4.0.0-alpha3~1^2~3
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d99bf81cd6ae330c1da0c49a6c88a9c777c85274;p=thirdparty%2Fpdns.git

document outgoing-axfr-expand-alias
---

diff --git a/docs/markdown/authoritative/settings.md b/docs/markdown/authoritative/settings.md
index 99eead07d6..2aa8529428 100644
--- a/docs/markdown/authoritative/settings.md
+++ b/docs/markdown/authoritative/settings.md
@@ -588,6 +588,18 @@ with untrusted users.
 The docs had previously indicated that the default was "no", but the default has
 been "yes" since 2005.
 
+## `outgoing-axfr-expand-alias`
+* Boolean
+* Default: no
+
+If this is enabled, ALIAS records are expanded (synthesised to their A/AAAA)
+during outgoing AXFR. This means slaves will not automatically follow changes
+in those A/AAAA records unless you AXFR regularly!
+
+If this is disabled (the default), ALIAS records are sent verbatim during
+outgoing AXFR. Note that if your slaves do not support ALIAS, they will return
+NODATA for A/AAAA queries for such names.
+
 ## `pipebackend-abi-version`
 * Integer
 * Default: 1