Mark Andrews 59d1eb3ff8 Add tests for forwarder cache poisoning scenarios ... - Check that an NS in an authority section returned from a forwarder which is above the name in a configured "forward first" or "forward only" zone (i.e., net/NS in a response from a forwarder configured for local.net) is not cached. - Test that a DNAME for a parent domain will not be cached when sent in a response from a forwarder configured to answer for a child. - Check that glue is rejected if its name falls below that of zone configured locally. - Check that an extra out-of-bailiwick data in the answer section is not cached (this was already working correctly, but was not explicitly tested before). (cherry picked from commit bf3fffff67)		2022-04-08 10:12:24 +02:00
..
local.net.db	Add tests for forwarder cache poisoning scenarios	2022-04-08 10:12:24 +02:00
local.tld.db	Add tests for forwarder cache poisoning scenarios	2022-04-08 10:12:24 +02:00
named1.conf.in	Add tests for forwarder cache poisoning scenarios	2022-04-08 10:12:24 +02:00
named2.conf.in	Add tests for forwarder cache poisoning scenarios	2022-04-08 10:12:24 +02:00
named3.conf.in	Add tests for forwarder cache poisoning scenarios	2022-04-08 10:12:24 +02:00
named4.conf.in	Add tests for forwarder cache poisoning scenarios	2022-04-08 10:12:24 +02:00
root.db	Add tests for forwarder cache poisoning scenarios	2022-04-08 10:12:24 +02:00