increased dns failures in unbound 1.22

[Klaas-]

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

• I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
• I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
I am having issues with dns, specifically with unbound 1.22 sometimes not giving answers where upstream dns answeres normally. It is being resolved by downgrading unbound to 1.21.1 from a previous opnsense release.

I've searched for problems upstream: there are some reports https://lists.nlnetlabs.nl/pipermail/unbound-users/2024-November/008427.html and some fixes have been incorporated into unbound master, will go into 1.23
If you want to look into backporting:
NLnetLabs/unbound@fd1a1d5
NLnetLabs/unbound@733d5f7

To Reproduce
So I can not reproduce this at will.

Expected behavior
DNS works

Relevant log files
It does not show up in log files in opnsense default log levels.

Additional context
I've reverted to unbound 1.21.1 and dns is running normal again

Environment
OPNsense 24.7.9_1-amd64
Intel(R) N200

[fichtner]

I would like to trust the good people of NLnetLabs with their release policy. They do have a good track record of releasing new versions as necessary.

Cheers,
Franco

[Klaas-]

okay, yeah no need to play with backporting, rolling back is easy enough -- for anyone else experiencing these issues: you can run opnsense-revert -r 24.7.6 unbound until a 1.23 is released and used in opnsense