The secret is created automatically if the user does not configure their own secret in the configuration.
This means that the workers will be able to resume each other's TLS sessions, regardless of whether the user has configured it to do so.
+- answer NOTIMPL for meta-types and non-IN RR classes (!1589)
+
Bugfixes
--------
- daemon/proxyv2: fix informing the engine about TCP/TLS from the actual client (!1578)
+
Knot Resolver 6.0.8 (2024-07-23)
================================
knot_pkt_t *ans = kr_request_ensure_answer(ctx->req);
if (!ans)
return ctx->req->state;
+ /* This RCODE is explicitly suggested for meta QTYPEs in RFC 8906 sec.7 */
knot_wire_set_rcode(ans->wire, KNOT_RCODE_NOTIMPL);
kr_request_set_extended_error(ctx->req, KNOT_EDNS_EDE_NOTSUP, "57CK");
return KR_STATE_DONE;