lib: proper key/ta checks in zone cut resolution
this fixes problems with servers authoritative both for parent and child zone and vice versa as the DS is authoritative parent-side, a full subrequest is launched. this breaks some tests that don’t have a full referral path todo bugs: - non-existence proof with only SOA and no NS is not correctly resolved - revalidation in some cases causes record duplication - NS queries with DO=1 answered from cache are not correctly resolved, as the TA is not set at this time
Showing
Please register or sign in to comment