From: Josh Soref Date: Thu, 2 Feb 2017 09:51:30 +0000 (+0000) Subject: spelling: explicitly X-Git-Tag: rec-4.1.0-alpha1~291^2~60 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0efecd70690867ad176eb03c32ee4e2c2d037e84;p=thirdparty%2Fpdns.git spelling: explicitly --- diff --git a/docs/markdown/authoritative/settings.md b/docs/markdown/authoritative/settings.md index 3f81c18340..69fc8686c9 100644 --- a/docs/markdown/authoritative/settings.md +++ b/docs/markdown/authoritative/settings.md @@ -599,7 +599,7 @@ hostnames to check their IP addresses against the specfied whitelist. The resolv may take considerable time, especially if those hostnames are slow to resolve. If you do not need to NOTIFY the slaves defined in the NS records (e.g. you are using another method to distribute the zone data to the slaves), then set `only-notify` to an empty -value and specify the notification targets explicitely using [`also-notify`](#also-notify) +value and specify the notification targets explicitly using [`also-notify`](#also-notify) and/or `ALSO-NOTIFY` domain metadata to avoid this potential bottleneck. ## `out-of-zone-additional-processing` diff --git a/pdns/README-dnsdist.md b/pdns/README-dnsdist.md index 95442f4c3d..cb69430e4f 100644 --- a/pdns/README-dnsdist.md +++ b/pdns/README-dnsdist.md @@ -1127,7 +1127,7 @@ that can arise in this kind of setup: it might be confused by the fact that the source address will be the one from the `dnsdist` server. -The first issue can be solved by routing SOA, AXFR and IXFR requests explicitely +The first issue can be solved by routing SOA, AXFR and IXFR requests explicitly to the master: ```