Date: Tue, 19 Sep 2023 12:37:48 +0200 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@FreeBSD.org> To: Doug Hardie <bc979@lafn.org> Cc: Alain Zscheile <fogti+fbsd@ytrizja.de>, freebsd-stable@freebsd.org Subject: Re: local-unbound stopped working after upgrade to 13.2 Message-ID: <86v8c6qwhv.fsf@ltc.des.no> In-Reply-To: <86B400F5-01AB-4623-BAF0-6332E3B0CA2F@sermon-archive.info> (Doug Hardie's message of "Tue, 19 Sep 2023 03:08:27 -0700") References: <1a11ae16-7425-6d5a-c864-0005343b678c@ytrizja.de> <e32c9db93b537a2839e99b8ec1fba3e2@bsdforge.com> <413c02d2-89bd-96c7-5999-ee789b6ed97b@ytrizja.de> <61C47FC1-43A5-4511-A034-D89E60DFF10E@sermon-archive.info> <867comscqv.fsf@ltc.des.no> <86B400F5-01AB-4623-BAF0-6332E3B0CA2F@sermon-archive.info>
index | next in thread | previous in thread | raw e-mail
Doug Hardie <bc979@lafn.org> writes: > The only issue I encountered with local unbound some years ago was it > didn't support local-zone which I needed. It does. Just put it in a separate file in /var/unbound/conf.d/. You may need to adjust your access control settings as well. For instance, I use this to allow local-unbound on my desktop computer to also serve NATed bhyve VMs: % cat /var/unbound/conf.d/access-control.conf server: interface: 127.0.0.1 access-control: 127.0.0.0/24 allow interface: 192.168.144.1 access-control: 192.168.144.0/24 allow DES -- Dag-Erling Smørgrav - des@FreeBSD.orghelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86v8c6qwhv.fsf>