ComputerSurge/bind9
3
0
Fork 0
Code Pull Requests 1 Activity

Increase migrate.kasp DNSKEY TTL

Browse Source 
Increate the DNSKEY TTL of the migrate.kasp zone for the following
reason:  The key states are initialized depending on the timing
metadata. If a key is present long enough in the zone it will be
initialized to OMNIPRESENT.  Long enough here is the time when it
was published (when the setup script was run) plus DNSKEY TTL.
Otherwise it is set to RUMOURED, or to HIDDEN if no timing metadata
is set or the time is still in the future.

Since the TTL is "only" 5 minutes, the DNSKEY state may be
initialized to OMNIPRESENT if the test is slow, but we expect it
to be in RUMOURED state.  If we increase the TTL to a couple of
hours it is very unlikely that it will be initialized to something
else than RUMOURED.

(cherry picked from commit 04e6711029)
This commit is contained in:
Matthijs Mekking
2020-04-07 15:51:43 +02:00
parent 02a2de8adb
commit 0d050323c0
3 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
bin/tests/system/kasp/tests.sh
View File

@@ -2893,7 +2893,7 @@ check_next_key_event 3600
# Testing good migration.
#
set_zone "migrate.kasp"
set_policy "none" "2" "300"
set_policy "none" "2" "7200"
set_server "ns6" "10.53.0.6"
init_migration_match() {
@@ -3090,7 +3090,7 @@ next_key_event_threshold=$((next_key_event_threshold+i))
# Testing migration.
#
set_zone "migrate.kasp"
set_policy "migrate" "2" "300"
set_policy "migrate" "2" "7200"
set_server "ns6" "10.53.0.6"
# Key properties, timings and metadata should be the same as legacy keys above.