From 038b3cd468a6aa4d5feb38826eee256ba223fa72 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ond=C5=99ej=20Sur=C3=BD?= Date: Fri, 28 Nov 2025 15:13:58 +0100 Subject: [PATCH] Add more information to the rndc recursing output about fetches It is possible to have a fetch that is active, but it has been cloned, so it won't be used when found in the hash table. The fetch options also prevent matching in the hash table, so add a hexadecimal dump of the fctx->options to the output. (cherry picked from commit 23ae5544beb28b42611168d96bfc5ab9c9ef283e) --- lib/dns/resolver.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/lib/dns/resolver.c b/lib/dns/resolver.c index 49e53da36a..f872c56588 100644 --- a/lib/dns/resolver.c +++ b/lib/dns/resolver.c @@ -11179,9 +11179,11 @@ dns_resolver_dumpfetches(dns_resolver_t *res, isc_statsformat_t format, dns_rdatatype_format(fctx->type, typebuf, sizeof(typebuf)); - fprintf(fp, "/%s (%s): started %s, ", typebuf, - fctx->state == fetchstate_active ? "active" : "done", - timebuf); + fprintf(fp, "/%s (%s), 0x%x: started %s, ", typebuf, + fctx->state == fetchstate_done ? "done" + : fctx->cloned ? "cloned" + : "active", + fctx->options, timebuf); for (resp = ISC_LIST_HEAD(fctx->resps); resp != NULL; resp = ISC_LIST_NEXT(resp, link))