-
-
Notifications
You must be signed in to change notification settings - Fork 367
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1221 from NLnetLabs/bugfix/consider-auth-zones-wh…
…en-forwarding Consider auth zones when checking for forwarders
- Loading branch information
Showing
3 changed files
with
195 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,155 @@ | ||
; config options | ||
server: | ||
target-fetch-policy: "0 0 0 0 0" | ||
|
||
auth-zone: | ||
name: "example.tld." | ||
for-upstream: yes | ||
for-downstream: no | ||
fallback-enabled: no | ||
## this line generates zonefile: "/tmp/xxx.example.tld" | ||
zonefile: | ||
TEMPFILE_NAME example.tld | ||
## this is the inline file /tmp/xxx.example.tld | ||
## the tempfiles are deleted when the testrun is over. | ||
TEMPFILE_CONTENTS example.tld | ||
$ORIGIN tld. | ||
example 3600 IN SOA a b 1 2 3 4 5 | ||
3600 IN NS ns.example.tld. | ||
$ORIGIN example.tld. | ||
ns 3600 IN A 1.2.3.4 | ||
www 3600 IN A 3.3.3.3 | ||
more 3600 IN NS ns.more.tld. | ||
TEMPFILE_END | ||
|
||
forward-zone: | ||
name: "." | ||
forward-addr: 9.9.9.9 | ||
|
||
stub-zone: | ||
name: "tld" | ||
stub-addr: 2.3.4.5 | ||
stub-zone: | ||
name: "more.example.tld" | ||
stub-addr: 2.3.4.7 | ||
CONFIG_END | ||
|
||
SCENARIO_BEGIN Test iterator's ability to route the request to the correct, configured delegation point | ||
; Preference should be auth-zone > stub-zone > forward-zone | ||
; But configuration-wise, since everything is an entry on the forwards tree | ||
; (or a hole in the case of stub/auth), forwards cannot be replaced by | ||
; stubs/auth. | ||
; Also stub/auth zones end the part of the tree that gets forwarded, e.g., | ||
; delegations from an auth/stub cannot be caught by a higher forwarder, it will | ||
; be recursively resolved instead. | ||
|
||
; '.' forwarder | ||
RANGE_BEGIN 0 100 | ||
ADDRESS 9.9.9.9 | ||
ENTRY_BEGIN | ||
MATCH opcode qtype qname | ||
ADJUST copy_id | ||
REPLY QR NOERROR | ||
SECTION QUESTION | ||
www.deleg.tld. IN A | ||
SECTION ANSWER | ||
www.deleg.tld. IN A 3.3.3.3 | ||
ENTRY_END | ||
|
||
ENTRY_BEGIN | ||
MATCH opcode qtype qname | ||
ADJUST copy_id | ||
REPLY QR NOERROR | ||
SECTION QUESTION | ||
www.more.example.tld. IN A | ||
SECTION ANSWER | ||
www.more.example.tld. IN A 3.3.3.3 | ||
ENTRY_END | ||
RANGE_END | ||
|
||
; 'tld.' stub server | ||
RANGE_BEGIN 0 100 | ||
ADDRESS 2.3.4.5 | ||
ENTRY_BEGIN | ||
MATCH opcode qtype qname | ||
ADJUST copy_id | ||
REPLY QR AA NOERROR | ||
SECTION QUESTION | ||
www.tld. IN A | ||
SECTION ANSWER | ||
www.tld. IN A 3.3.3.3 | ||
ENTRY_END | ||
RANGE_END | ||
|
||
; 'more.example.tld.' stub server | ||
RANGE_BEGIN 0 100 | ||
ADDRESS 2.3.4.7 | ||
ENTRY_BEGIN | ||
MATCH opcode qtype qname | ||
ADJUST copy_id | ||
REPLY QR AA NOERROR | ||
SECTION QUESTION | ||
www.more.example.tld. IN A | ||
SECTION ANSWER | ||
www.more.example.tld. IN A 3.3.3.3 | ||
ENTRY_END | ||
RANGE_END | ||
|
||
; query www.tld ... | ||
STEP 1 QUERY | ||
ENTRY_BEGIN | ||
REPLY RD | ||
SECTION QUESTION | ||
www.tld. IN A | ||
ENTRY_END | ||
|
||
; ... answer should come from 'tld.' stub zone | ||
STEP 2 CHECK_ANSWER | ||
ENTRY_BEGIN | ||
MATCH all | ||
REPLY QR RD RA NOERROR | ||
SECTION QUESTION | ||
www.tld. IN A | ||
SECTION ANSWER | ||
www.tld. IN A 3.3.3.3 | ||
ENTRY_END | ||
|
||
; query www.example.tld ... | ||
STEP 3 QUERY | ||
ENTRY_BEGIN | ||
REPLY RD | ||
SECTION QUESTION | ||
www.example.tld. IN A | ||
ENTRY_END | ||
|
||
; ... answer should come from 'example.tld.' auth zone | ||
STEP 4 CHECK_ANSWER | ||
ENTRY_BEGIN | ||
MATCH all | ||
REPLY QR RD RA NOERROR | ||
SECTION QUESTION | ||
www.example.tld. IN A | ||
SECTION ANSWER | ||
www.example.tld. IN A 3.3.3.3 | ||
ENTRY_END | ||
|
||
; query www.more.example.tld ... | ||
STEP 5 QUERY | ||
ENTRY_BEGIN | ||
REPLY RD | ||
SECTION QUESTION | ||
www.more.example.tld. IN A | ||
ENTRY_END | ||
|
||
; ... answer should come from 'more.example.tld.' stub zone | ||
STEP 6 CHECK_ANSWER | ||
ENTRY_BEGIN | ||
MATCH all | ||
REPLY QR RD RA NOERROR | ||
SECTION QUESTION | ||
www.more.example.tld. IN A | ||
SECTION ANSWER | ||
www.more.example.tld. IN A 3.3.3.3 | ||
ENTRY_END | ||
|
||
SCENARIO_END |