Date: Mon, 18 Sep 2023 17:55:54 +0200 From: Yuri <yuri@aetern.org> To: stable@freebsd.org Subject: Re: local-unbound stopped working after upgrade to 13.2 Message-ID: <c394f074-3474-4bb6-8534-ed2400029010@aetern.org> In-Reply-To: <6285865612f654686892dfd2ff88aa24@bsdforge.com> References: <1a11ae16-7425-6d5a-c864-0005343b678c@ytrizja.de> <e32c9db93b537a2839e99b8ec1fba3e2@bsdforge.com> <82a8ed8b-c3e5-421a-b089-725a044b5ee4@aetern.org> <6285865612f654686892dfd2ff88aa24@bsdforge.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Chris wrote: > On 2023-09-18 08:26, Yuri wrote: >> Chris wrote: >>> On 2023-09-17 11:15, Alain Zscheile wrote: >>>> Hi, >>>> >>>> After upgrading from FreeBSD-13.1 to 13.2 I noticed that local-unbound >>>> doesn't >>>> appear to work anymore >>>> (doesn't return DNS responses for anything, although I don't have >>>> network traces). >>>> >>>> For now, I just disabled it on all my systems, but I believe this is a >>>> bug that >>>> should be fixed... >>> >>> This is more likely a ports issue and would be better served on the >>> ports@ list. >> >> local-unbound is in bsae. > You mean base, right? ;-) > Sure. But it's derived from the source in ports. Maybe CC ports@ ? No, the source is in contrib/unbound, has its own set of build rules and the changes between 13.1 and 13.2 can be easily seen using git, don't see how ports are related.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c394f074-3474-4bb6-8534-ed2400029010>