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

Add two checkds test servers

Browse Source 
Add two new checkds test servers, that are hidden secondaries (hidden
as in not published in the NS RRset), that can be used specifically
for testing explicitly configured parental-agents.
This commit is contained in:
Matthijs Mekking
2023-03-28 16:47:16 +02:00
parent a921cabb8c
commit 47f7cb0a36
8 changed files with 271 additions and 67 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
bin/tests/system/checkds/README
View File

@@ -12,19 +12,28 @@ information regarding copyright ownership.
The test setup for the checkds tests.
These servers are parent servers:
- ns1 is the root server.
- ns2 is a primary authoritative server that serves the parent zone for zones
configured in ns9.
- ns3 is a resolver that can be configured as a parental agent.
- ns4 is the secondary server for ns2.
- ns8 is the secondary server for ns2 that is not part of the NS RRset,
used for testing explicit parental-agents.
- ns5 is a primary authoritative server that serves the parent zone for zones
configured in ns9, but this one does not publish DS records (to test cases
where the DS is missing).
where the DS is missing and the DS needs to be withdrawn).
- ns7 is the secondary server for ns5.
- ns10 is the secondary server for ns5 that is not part of the NS RRset,
used for testing explicit parental-agents.
- ns6 is an authoritative server for a different zone, to test badly configured
parental agents.
- ns7 is the secondary server for ns5.
Finally, ns9 is the authoritative server for the various DNSSEC enabled test
domains.
- ns3 is a resolver that can be configured as a parental agent.
- Finally, ns9 is the authoritative server for the various DNSSEC enabled test
domains.
We need multiple test cases for testing the "checkds" functionality. Basically,
the behavior of "checkds" is of importance in three cases: