From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: unbound 1.15.0 - problems with certain DoT(?) configurations
Date: Fri, 11 Feb 2022 09:36:10 +0000 [thread overview]
Message-ID: <BB90C5E9-09B6-4278-9F67-87D0A9D096D6@ipfire.org> (raw)
In-Reply-To: <a1530bff-5130-5ab9-81e5-6cb6654c1690@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 917 bytes --]
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(a)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>
next parent reply other threads:[~2022-02-11 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a1530bff-5130-5ab9-81e5-6cb6654c1690@ipfire.org>
2022-02-11 9:36 ` Michael Tremer [this message]
2022-04-18 20:47 ` Peter Müller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BB90C5E9-09B6-4278-9F67-87D0A9D096D6@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox