From afa4f89d1be860bd84927fd05e056545bfc721a4 Mon Sep 17 00:00:00 2001 From: Jan-Piet Mens Date: Wed, 4 Nov 2015 08:27:53 +0100 Subject: [PATCH] clarify DNSSEC in geoip-backend from tips by @cmouse --- docs/markdown/authoritative/backend-geoip.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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. -- 2.40.0