...
 
Commits (23)
[flake8]
max-line-length=100
......@@ -3,3 +3,4 @@
*~
config.ini
dnssec_keys_management.ini
This diff is collapsed.
This diff is collapsed.
[dnssec]
# Directory where dnssec keys will be stored. This directory will contain on subdirectory per DNS
# zone, containing dnssec keys.
base_directory=/etc/bind/keys
# Interval between 2 operations on the dns keys.
# For example if you have KEY1 enabled, KEY2 is published INTERVAL before disabling KEY1. KEY1 is
# disabled when KEY2 is activated, KEY2 is deleted INTERVAL after being disabled.
# INTERVAL MUST be greater than the longest TTL that the DS records can have
# INTERVAL MUST also be higher in the bind signature interval (default 22.5 days)
# This mainly depents of the parent zone configuration and you do not necessarily have
# disabled when KEY2 is activated, KEY1 is deleted INTERVAL after being disabled.
# INTERVAL MUST be greater than the longest TTL DS records can have.
# INTERVAL MUST also be higher than the bind signature interval (default 22.5 days)
# This partially depends of the parent zone configuration and you do not necessarily have
# control over it.
interval=23
# Time after which a ZSK is replaced by a new ZSK.
# Generation of ZSK and activation / deactivation / deletion is managed automatically as long as
# routine.py -c is called at least once a day.
# dnssec_keys_management.py -c is called at least once a day.
zsk_validity=30
# Time after which a new KSK is generated and published for the zone (and activated after INTERVAL).
# The old key is removed only INTERVAL after the new key was routine.py --ds-seen. This usually
# requires a manual operation with the registrar (publish DS of the new key in the parent zone).
# routine.py -c displays a message as long as --ds-seen needs to be called and has not yet be called
# The old key is removed only INTERVAL after the new key was dnssec_keys_management.py --ds-seen.
# This usually requires a manual operation with the registrar (publish DS of the new key
# in the parent zone). dnssec_keys_management.py -c displays a message as long as --ds-seen needs
# to be called and has not yet be called
ksk_validity=366
# Algorithm used to generate new keys. Only the first created KSK and ZSK of a zone will use
# this algorithm. Any renewing key will use the exact same parameters (name, algorithm, size,
# and type) as the renewed key.
# Valid algorithms are RSASHA256, RSASHA512, ECCGOST, ECDSAP256SHA256, ECDSAP384SHA384.
algorithm=RSASHA256
# Size of the created KSK. Only the first created KSK of a zone will use this size.
# Any renewing key will use the exact same parameters (name, algorithm, size, and type)
# as the renewed key.
ksk_size=2024
# Size of the created ZSK. Only the first created ZSK of a zone will use this size.
# Any renewing key will use the exact same parameters (name, algorithm, size, and type)
# as the renewed key.
zsk_size=1024
[path]
......
This diff is collapsed.