lib/resolve, modules: NO_ANSWER for not responding to clients

Closes #432 (closed)

added 1 commit

• 0cf22e1e - lib/resolve, modules: NO_ANSWER for not responding to clients

Compare with previous version

added feature label

added 1 commit

• 9bf0145f - fixup! lib/resolve, modules: NO_ANSWER for not responding to clients

Compare with previous version

Now when I was looking at the code around, I realized that we already had an internal mechanism for dropping answers. It uses kr_request::answer == NULL as the trigger, so I expect we'd better reuse that instead of adding a new flag.

We needed it for... technical reasons, as in some cases it may not be possible to get a buffer for the packet. Those changes should be contained in !1083 (commits)

added 1 commit

• 158039aa - fixup! lib/resolve, modules: NO_ANSWER for not responding to clients

Compare with previous version

resolved all threads

approved this merge request

added 1 commit

• d64a463a - lib/resolve, modules: NO_ANSWER for not responding to clients

Compare with previous version

marked this merge request as ready

added 3 commits

• d64a463a...cd4a1212 - 2 commits from branch master
• 2fb5f7bd - lib/resolve, modules: NO_ANSWER for not responding to clients

Compare with previous version

added 3 commits

• 2fb5f7bd...a5dffe2f - 2 commits from branch master
• 805c5d3e - lib/resolve, modules: NO_ANSWER for not responding to clients

Compare with previous version

resolved all threads

added 1 commit

• f9391074 - fixup! lib/resolve, modules: NO_ANSWER for not responding to clients

Compare with previous version

marked this merge request as draft from f9391074

added 1 commit

• fd699500 - lib/resolve, modules: NO_ANSWER for not responding to clients

Compare with previous version

marked this merge request as ready

added 12 commits

• fd699500...ac1d732f - 11 commits from branch master
• 334ee4f4 - lib/resolve, modules: NO_ANSWER for not responding to clients

Compare with previous version

merged