2 ; config options go here.
3 forward-zone: name: "." forward-addr: 216.0.0.1
6 SCENARIO_BEGIN Untrusted rrset not used for update
14 ; the query is sent to the forwarder - no cache yet.
15 STEP 2 CHECK_OUT_QUERY
17 MATCH qname qtype opcode
23 MATCH opcode qtype qname
25 ; authoritative answer
26 REPLY QR AA RD RA NOERROR
30 www.example.com. IN A 10.20.30.40
32 example.com. IN NS ns.example.com.
34 ns.example.com. IN A 10.20.30.50
43 www.example.com. IN A 10.20.30.40
45 example.com. IN NS ns.example.com.
47 ns.example.com. IN A 10.20.30.50
50 ; another query passes along
57 STEP 7 CHECK_OUT_QUERY
59 MATCH qname qtype opcode
64 ; This answer has updated information on ns2.example.com.
65 ; But it is nerfed into the additional. Must be ignored per rfc2181.
67 MATCH opcode qtype qname
69 ; authoritative answer
70 REPLY QR AA RD RA NOERROR
74 bla.example.com. IN A 10.20.30.140
77 example.com. IN NS ns.eeeek.com.
78 example.com. IN NS ns2.eeeek.com.
79 ns.eeeek.com. IN A 55.44.33.22
80 ns2.eeeek.com. IN A 55.44.33.24
89 bla.example.com. IN A 10.20.30.140
95 ; original www.example.com query
100 www.example.com. IN A
102 ; immediate answer without an OUT_QUERY happening (checked on exit)
103 ; also, the answer does not have AA set
104 ; NS rrset has not been updated from the additional seen before.
110 www.example.com. IN A
112 www.example.com. IN A 10.20.30.40
114 example.com. IN NS ns.example.com.
116 ns.example.com. IN A 10.20.30.50