Commit 26bcd8c1 authored by Vladimír Čunát's avatar Vladimír Čunát Committed by Tomas Krizek

rebinding: change/fix when triggered inside sub-query

This avoids getting into an inconsistent state of the request (assert),
and it also allows some real-life cases to succeed without using
a forbidden address in any way (even though they *are* weird).

I can still imagine weird setups where a request gets failed even
though it would be resolvable without *using* a forbidden address,
but none of these seem reasonable anyway (or common in practice).
parent b44c0785
Pipeline #51192 canceled with stages
in 2 minutes and 22 seconds
......@@ -104,7 +104,14 @@ function M.layer.consume(state, req, pkt)
qry.flags.RESOLVED = 1 -- stop iteration
qry.flags.CACHED = 1 -- do not cache
--[[ In case we're in a sub-query, we do not touch the final req answer.
Only this sub-query will get finished without a result - there we
rely on the iterator reacting to flags.RESOLVED
Typical example: NS address resolution -> only this NS won't be used
but others may still be OK (or we SERVFAIL due to no NS being usable).
if qry.parent == nil then refuse(req) end
if verbose() then
ffi.C.kr_log_qverbose_impl(qry, 'rebinding',
'blocking blacklisted IP in RR \'%s\' received from IP %s\n',
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment