First Last Prev Next    This bug is not in your last search results.
Bug 55163 - UCS 5.0 DNS "resolver priming query complete"
UCS 5.0 DNS "resolver priming query complete"
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: DNS
UCS 5.0
Other Linux
: P5 normal (vote)
: UCS 5.0-2-errata
Assigned To: Philipp Hahn
Erik Damrose
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2022-09-02 11:07 CEST by Mirac Erdemiroglu
Modified: 2022-10-12 17:49 CEST (History)
4 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.046
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2022081721000409, 2022082921000324
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mirac Erdemiroglu univentionstaff 2022-09-02 11:07:44 CEST 
UCS 5.0-2 errata 397


since the update to UCS 5 the syslog/daemon-log is extremely filled with messages from the named.
Almost every second the message
  "resolver priming query complete"

In the internet you can only find outdated bind9 bugs.
Comment 1 Philipp Hahn univentionstaff 2022-09-02 11:20:22 CEST 
2022-08-17 @dschnick already asked about this <https://chat.univention.de/channel/tech?msg=qDNA2nECXM2MnjinQ>:

> A customer is complaining logspam of bind in ucs 5. `named[5116]: resolver priming query complete` is logged every few seconds. I searched and found that it seems to be a bug in bind9: https://unix.stackexchange.com/questions/450234/named862-resolver-priming-query-complete-every-20-seconds or 
> https://gitlab.isc.org/isc-projects/bind9/-/issues/752
>
> There is stated 9.13 is fixed; we are using 9.11 unfixed. But I see in buster-backports we could use 9.16
> https://packages.debian.org/search?keywords=bind9
> 
> Will we do that? Should I open a bug for it? I'm sure changing bind is nothing we will do on the fly. Are there already plans how to deal with bind?

And here my answer:

> UCS-5.0 will probably continue to use BIND9 `9.11.5.P4` from Debian-10-Buster; switching to BIND9 `9.16` (from `buster-backports` using version from Debian-11-Bullseye) is not planned.
> As we patch BIND anyway we can try to backport [!1296](https://gitlab.isc.org/isc-projects/bind9/-/merge_requests/1296) ourselves if someone up the food-chain makes it a priority.
Comment 2 Philipp Hahn univentionstaff 2022-10-10 18:05:27 CEST 
r19705 | Bug #55163: backport b49310ac06a

Package: bind9
Version: 1:9.11.5.P4+dfsg-5.1+deb10u8A~5.0.2.202210101801
Branch: ucs_5.0-0
Scope: errata5.0-2
Comment 3 Philipp Hahn univentionstaff 2022-10-12 17:12:21 CEST 
tail -f /var/log/daemon.log &
for dom in gooogle.com. univention.de. univention.org. univention.com. microsoft.com. apple.com. github.com. gitlab.com. gitlab.org
do
  dig @localhost "$dom"
done

OLD: "resolver priming query complete" for every domain
NEW: only once

[5.0-2] 92b433c3f2 Bug #55253: bind9 1:9.11.5.P4+dfsg-5.1+deb10u8A~5.0.2.202210101801
 doc/errata/staging/bind9.yaml | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)
Comment 4 Erik Damrose univentionstaff 2022-10-12 17:19:08 CEST 
OK: applying 0018-Bug-55163-fix-resolver-priming-query.quilt
OK: yaml
OK: Only one "resolver priming query complete" in daemon.log with new package version and the reproducer from comment 3

Verified
First Last Prev Next    This bug is not in your last search results.