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.

diff --git a/NEWS b/NEWS
index ae95ca41699e32831995057fda6efa6dd354f1fe..6246e7abfab6dc9637dc9add1ac3b46d5d0dbef5 100644 (file)
--- 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 6ba549cd3772fc703e37ffcd938d03284317d9aa..ed8ac5a219b8981bea5052c9d838789431e02eed 100644 (file)
--- 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 */