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

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

Browse Source
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
Download Patch File Download Diff File Expand all files Collapse all files

4
bin/tests/system/dnssec/ns3/dname-at-apex-nsec3.example.db.in Normal file
View File

@@ -0,0 +1,4 @@
$TTL 600
@ SOA ns3.example. . 1 1200 1200 1814400 3600
@ NS ns3.example.
@ DNAME example.

5
bin/tests/system/dnssec/ns3/named.conf.in
View File

@@ -294,6 +294,11 @@ zone "revkey.example" {
file "revkey.example.db.signed";
};
zone "dname-at-apex-nsec3.example" {
type master;
file "dname-at-apex-nsec3.example.db.signed";
};
include "siginterval.conf";
include "trusted.conf";

11
bin/tests/system/dnssec/ns3/sign.sh
View File

@@ -543,3 +543,14 @@ zsk1=`$KEYGEN -q -a RSASHA1 -3 $zone`
cat $infile ${ksk1}.key ${ksk2}.key ${zsk1}.key >$zonefile
$SIGNER -P -o $zone $zonefile > /dev/null 2>&1
#
# Check that NSEC3 are correctly signed and returned from below a DNAME
#
zone=dname-at-apex-nsec3.example
infile=dname-at-apex-nsec3.example.db.in
zonefile=dname-at-apex-nsec3.example.db
kskname=`$KEYGEN -q -a RSASHA256 -3fk $zone`
zskname=`$KEYGEN -q -a RSASHA256 -3 $zone`
cat $infile $kskname.key $zskname.key >$zonefile
$SIGNER -P -3 - -o $zone $zonefile > /dev/null 2>&1