From 27b6e14b258a578f293e1ed6006369e324049126 Mon Sep 17 00:00:00 2001 From: Ruben Date: Wed, 24 Jul 2013 08:37:53 +0200 Subject: [PATCH] Update pdns.xml Small update to docs, spotted by sid3windr --- pdns/docs/pdns.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pdns/docs/pdns.xml b/pdns/docs/pdns.xml index 0792838cbe..c49b27e34f 100755 --- a/pdns/docs/pdns.xml +++ b/pdns/docs/pdns.xml @@ -13384,7 +13384,6 @@ sql> insert into domainmetadata (domain_id, kind, content) values (7,'ALLOW-AXFR RFC2136 Support (Dynamic DNS Update) Starting with the PowerDNS Authoritative Server 3.4, RFC2136 support is available. There are a number of items NOT supported: - When operating as slave for a zone, forwarding to master is not supported. (Chapter 6 of RFC2136); There is no support for GSS-TSIG and SIG (TSIG is supported); WKS records are specifically mentioned in the RFC, we don't specifically care about WKS records; Anything we forgot.... @@ -13424,9 +13423,10 @@ sql> insert into domainmetadata (domain_id, kind, content) values (7,'ALLOW-AXFR forward-2136 [=yes] - Tell PowerDNS to forward 2136 to the master server if the zone is configured as slave. Masters are determined by the masters field in the domains table. + Tell PowerDNS to forward to the master server if the zone is configured as slave. Masters are determined by the masters field in the domains table. The default behaviour is enabled (yes), which means that it will try to forward. In the processing of the update packet, the allow-2136-from and TSIG-2136-ALLOW are processed first, so those permissions apply before the forward-2136 is used. + It will try all masters that you have configured until one is succesful. -- 2.47.2