Hello Matthias, hello Michael,

looking at https://lists.nlnetlabs.nl/pipermail/unbound-users/2022-February/007671.html, it appears as if the commit in question never made it into the final release of Unbound 1.15.0, so the issue should not appear with the productive version.

Unless I overlooked something, I would consider Unbound 1.15.0 to be ready for prime time. :-)

Thanks, and best regards, Peter Müller

Hello Matthias,

Yes, we should definitely wait before we introduce a known regression.

I do not see anything on the change log that would be *that* interesting for us that it would be worth it to break DoT.

Hopefully a patch will be available soon.

-Michael

...

On 11 Feb 2022, at 08:58, Matthias Fischer matthias.fischer@ipfire.org wrote:

Hi,

please note - I'm working on 'unbound 1.15.0' which was published yesterday, but it seems this version has some problems with DoT(?).

See: => https://lists.nlnetlabs.nl/pipermail/unbound-users/2022-February/007669.html

"It looks like with certain (dot?) configuration, 53/tcp becomes defunct on this version of unbound".

I'm testing - no problems so far - under MY environment (see attached screenshot).

Should we still wait?

=> Opinions!?

Best, Matthias<screenshot_dns_gui.png>