From: Jan-Piet Mens Date: Wed, 4 Nov 2015 07:27:53 +0000 (+0100) Subject: clarify DNSSEC in geoip-backend X-Git-Tag: dnsdist-1.0.0-alpha1~253^2~1 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=afa4f89d1be860bd84927fd05e056545bfc721a4;p=pdns clarify DNSSEC in geoip-backend from tips by @cmouse --- diff --git a/docs/markdown/authoritative/backend-geoip.md b/docs/markdown/authoritative/backend-geoip.md index f65fdaf6d..7b898237f 100644 --- a/docs/markdown/authoritative/backend-geoip.md +++ b/docs/markdown/authoritative/backend-geoip.md @@ -36,7 +36,7 @@ options described [here](https://github.com/maxmind/geoip-api-c/blob/master/READ Specifies the full path of the zone configuration file to use. ### `geoip-dnssec-keydir` -Specifies the full path of a directory that will contain DNSSEC keys. +Specifies the full path of a directory that will contain DNSSEC keys. This option enables DNSSEC on the backend. Keys can be created/managed with `pdnutil`, and the backend stores these keys in files with key flags and active/disabled state encoded in the key filenames. ## Zonefile format Zone configuration file uses YAML syntax. Here is simple example. Note that the ‐ before certain keys is part of the syntax.