Add a note about pregenarating keys for key rolls

With dnssec-policy you can pregenerate keys and if they are eligible,
rather than creating a new key, a key is selected from the pregenerated
keys. A key is eligible if it is unused, i.e it has no key timing
metadata set.

diff --git a/doc/arm/dnssec.inc.rst b/doc/arm/dnssec.inc.rst
index 732e2debd580df4cac01934621665fa43687037e..0b59dc37e7a69097464c2f16c7ca74feb566d6d2 100644 (file)
--- a/doc/arm/dnssec.inc.rst
+++ b/doc/arm/dnssec.inc.rst
@@ -196,6 +196,11 @@ To roll a key sooner than scheduled, or to roll a key that
 has an unlimited lifetime, use:
 :option:`rndc dnssec -rollover -key 12345 dnssec.example. <rndc dnssec>`.
 
+You can pregenerate keys and save them in the key directory. As long as the
+key has no timing metadata set, it may be selected as a successor in the
+upcoming key rollover. To pregenerate keys without setting key timing metadata,
+use the `-G` option: ``dnssec-keygen -G dnssec.example.``.
+
 To revert a signed zone back to an insecure zone, change
 the zone configuration to use the built-in "insecure" policy. Detailed
 instructions are described in :ref:`revert_to_unsigned`.