From 6214db808186587dbdc46854124dbf214d7a4261 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Vladim=C3=ADr=20=C4=8Cun=C3=A1t?= Date: Wed, 20 Aug 2025 09:11:38 +0200 Subject: [PATCH] lib/selection: respect 0x20 settings even after TCP issues Thankfully we can pull it from kr_request, as policy.FLAGS() also sets it in there. --- NEWS | 4 ++++ lib/selection.c | 2 +- 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/NEWS b/NEWS index ae95ca416..6246e7abf 100644 --- a/NEWS +++ b/NEWS @@ -5,6 +5,10 @@ Improvements ------------ - reduce validation strictness for domain names (#934, !1727) +Bugfixes +-------- +- /options/query-case-randomization: respect this even on TCP issues (!1732) + Knot Resolver 6.0.15 (2025-07-17) ================================= diff --git a/lib/selection.c b/lib/selection.c index 6ba549cd3..ed8ac5a21 100644 --- a/lib/selection.c +++ b/lib/selection.c @@ -648,7 +648,7 @@ void error(struct kr_query *qry, struct address_state *addr_state, case KR_SELECTION_TCP_CONNECT_FAILED: case KR_SELECTION_TCP_CONNECT_TIMEOUT: qry->server_selection.local_state->force_udp = true; - qry->flags.NO_0X20 = false; + qry->flags.NO_0X20 = qry->request->options.NO_0X20; /* Connection and handshake failures have properties similar * to UDP timeouts, so we handle them (almost) the same way. */ /* fall-through */ -- 2.47.3