From: Remi Gacogne Date: Tue, 14 Jun 2016 18:49:50 +0000 (+0200) Subject: dnsdist: Fix some typos in the AXFR/IXFR documentation X-Git-Tag: auth-4.0.0-rc1~40^2 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=refs%2Fpull%2F3992%2Fhead;p=thirdparty%2Fpdns.git dnsdist: Fix some typos in the AXFR/IXFR documentation --- diff --git a/pdns/README-dnsdist.md b/pdns/README-dnsdist.md index f27bb5fe80..c2b0fba029 100644 --- a/pdns/README-dnsdist.md +++ b/pdns/README-dnsdist.md @@ -994,8 +994,8 @@ receive AXFR or IXFR queries destined to this master. There are two issues that can arise in this kind of setup: * If the master is part of a pool of servers, the first SOA query can be directed - by `dnsdist` to a different server than the following AXFR/IXFR one. If all servers are not - perfectly synchronised at all times, it might to synchronisation issues. + by `dnsdist` to a different server than the following AXFR/IXFR one, which might + fail if the servers are not perfectly synchronised. * If the master only allows AXFR/IXFR based on the source address of the requestor, it might be confused by the fact that the source address will be the one from the `dnsdist` server. @@ -1008,7 +1008,7 @@ to the master: > addAction(OrRule({QTypeRule(dnsdist.SOA), QTypeRule(dnsdist.AXFR), QTypeRule(dnsdist.IXFR)}), PoolAction("master")) ``` -The second one might requires allowing AXFR/IXFR from the `dnsdist` source address +The second one might require allowing AXFR/IXFR from the `dnsdist` source address and moving the source address check on `dnsdist`'s side: ```