From: Peter van Dijk Date: Tue, 19 Apr 2016 12:46:36 +0000 (+0200) Subject: typo X-Git-Tag: dnsdist-1.0.0~4 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=0f1dbf7a3785b57fb76632f2fe70a3660fad8718;p=pdns typo --- diff --git a/docs/markdown/authoritative/backend-generic-sql.md b/docs/markdown/authoritative/backend-generic-sql.md index 6bcc02e78..f3037b21f 100644 --- a/docs/markdown/authoritative/backend-generic-sql.md +++ b/docs/markdown/authoritative/backend-generic-sql.md @@ -104,7 +104,7 @@ serial set to `0` in the database. The serial in SOA responses is set to the highest value of the `change_date` field in the "records" table. -# Handeling DNSSEC signed zones +# Handling DNSSEC signed zones To enable DNSSEC processing, the `backend-dnssec` option must be set to 'yes'. ## Rules for filling out DNSSEC fields diff --git a/docs/markdown/authoritative/dnssec.md b/docs/markdown/authoritative/dnssec.md index c58419960..cc4c3f7c9 100644 --- a/docs/markdown/authoritative/dnssec.md +++ b/docs/markdown/authoritative/dnssec.md @@ -294,7 +294,7 @@ changes in database schemas as shown in the [upgrade documentation](upgrading.md **Warning**: Once the relevant `backend-dnssec` switch has been set, stricter rules apply for filling out the database! The short version is: run `pdnsutil rectify-all-zones`, even those not secured with DNSSEC! For more -information, see the [DNSSEC documentation for Generic SQL backends](backend-generic-sql.md#handeling-dnssec-signed-zones). +information, see the [DNSSEC documentation for Generic SQL backends](backend-generic-sql.md#handling-dnssec-signed-zones). To deliver a correctly signed zone with the [DNSSEC defaults](#dnssec-defaults), invoke: