verify that dnssec-signzone generates NSEC3 records with DNAME at the apex

This commit is contained in:
Mark Andrews
2018-11-26 12:56:40 +11:00
parent 4ccff3bbed
commit 06e218c421
7 changed files with 39 additions and 7 deletions

View File

@@ -158,3 +158,5 @@ ns.managed-future A 10.53.0.3
revkey NS ns.revkey
ns.revkey A 10.53.0.3
dname-at-apex-nsec3 NS ns3

View File

@@ -24,7 +24,8 @@ for subdomain in secure badds bogus dynamic keyless nsec3 optout \
nsec3-unknown optout-unknown multiple rsasha256 rsasha512 \
kskonly update-nsec3 auto-nsec auto-nsec3 secure.below-cname \
ttlpatch split-dnssec split-smart expired expiring upper lower \
dnskey-unknown dnskey-nsec3-unknown managed-future revkey
dnskey-unknown dnskey-nsec3-unknown managed-future revkey \
dname-at-apex-nsec3
do
cp ../ns3/dsset-$subdomain.example$TP .
done