From 0efecd70690867ad176eb03c32ee4e2c2d037e84 Mon Sep 17 00:00:00 2001 From: Josh Soref Date: Thu, 2 Feb 2017 09:51:30 +0000 Subject: [PATCH] spelling: explicitly --- docs/markdown/authoritative/settings.md | 2 +- pdns/README-dnsdist.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/markdown/authoritative/settings.md b/docs/markdown/authoritative/settings.md index 3f81c1834..69fc8686c 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 95442f4c3..cb69430e4 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: ``` -- 2.50.1