Date: Tue, 19 Sep 2023 01:59:36 -0700 From: Doug Hardie <bc979@lafn.org> To: Alain Zscheile <fogti+fbsd@ytrizja.de> Cc: freebsd-stable@freebsd.org Subject: Re: local-unbound stopped working after upgrade to 13.2 Message-ID: <61C47FC1-43A5-4511-A034-D89E60DFF10E@sermon-archive.info> In-Reply-To: <413c02d2-89bd-96c7-5999-ee789b6ed97b@ytrizja.de> References: <1a11ae16-7425-6d5a-c864-0005343b678c@ytrizja.de> <e32c9db93b537a2839e99b8ec1fba3e2@bsdforge.com> <413c02d2-89bd-96c7-5999-ee789b6ed97b@ytrizja.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Sep 19, 2023, at 01:37, Alain Zscheile <fogti+fbsd@ytrizja.de> = wrote: >=20 > On 2023-09-18 17:21, Chris wrote: >=20 >> On 2023-09-17 11:15, Alain Zscheile wrote: >>> 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). >>>=20 >>> For now, I just disabled it on all my systems, but I believe this is = a bug that >>> should be fixed... >>=20 >> This is more likely a ports issue and would be better served on the = ports@ list. >> If you believe this to be a bug. You will get better results filing a = pr(1) at >> https://bugs.freebsd.org >=20 > Based upon what I've heard from others, the issue doesn't appear to be = present in ports' > dns/unbound. I have been running the unbound port (pkg) on FreeBSD-13.2 ever since = 13.2 became available. AMD64 with Intel processor. I have not = experienced any issues. It just works. Local unbound never worked for = what I needed. I don't know if that was a limitation of local unbound = or if there was an issue with it. The port worked so I stuck with it. -- Doug
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?61C47FC1-43A5-4511-A034-D89E60DFF10E>