From: Michał Kępień <michal@isc.org>
Date: Wed, 16 Feb 2022 12:26:12 +0000 (+0100)
Subject: Log the result of each resolver priming attempt
X-Git-Tag: v9.19.0~113^2~1
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=f286c845b03269443c3d395e6384858985127846;p=thirdparty%2Fbind9.git

Log the result of each resolver priming attempt

When a resolver priming attempt completes, the following message is
currently logged:

    resolver priming query complete

This message is identical for both successful and failed priming
attempts.  Consider the following log excerpts:

  - successful priming attempt:

        10-Feb-2022 11:33:11.272 all zones loaded
        10-Feb-2022 11:33:11.272 running
        10-Feb-2022 11:33:19.722 resolver priming query complete

  - failed priming attempt:

        10-Feb-2022 11:33:29.978 all zones loaded
        10-Feb-2022 11:33:29.978 running
        10-Feb-2022 11:33:38.432 timed out resolving '_.org/A/IN': 2001:500:9f::42#53
        10-Feb-2022 11:33:38.522 timed out resolving './NS/IN': 2001:500:9f::42#53
        10-Feb-2022 11:33:42.132 timed out resolving '_.org/A/IN': 2001:500:12::d0d#53
        10-Feb-2022 11:33:42.285 timed out resolving './NS/IN': 2001:500:12::d0d#53
        10-Feb-2022 11:33:44.685 resolver priming query complete

Include the result of each priming attempt in the relevant log message
to give the administrator better insight into named's resolver priming
process.
---

diff --git a/lib/dns/resolver.c b/lib/dns/resolver.c
index 0b5633f9fd8..b558485157c 100644
--- a/lib/dns/resolver.c
+++ b/lib/dns/resolver.c
@@ -10231,7 +10231,8 @@ prime_done(isc_task_t *task, isc_event_t *event) {
 
 	isc_log_write(dns_lctx, DNS_LOGCATEGORY_RESOLVER,
 		      DNS_LOGMODULE_RESOLVER, ISC_LOG_INFO,
-		      "resolver priming query complete");
+		      "resolver priming query complete: %s",
+		      isc_result_totext(fevent->result));
 
 	UNUSED(task);