Doug Hardie 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 allo
> On Sep 19, 2023, at 03:01, Dag-Erling Smørgrav wrote:
>
> Alain Zscheile writes:
>> After upgrading from FreeBSD-13.1 to 13.2 I noticed that local-unbound
>> doesn't
>> appear to work anymore [...]
>
> Doug Hardie writes:
>> Local unbound never worked for what I needed. [...]
>
> Normall
Alain Zscheile writes:
> After upgrading from FreeBSD-13.1 to 13.2 I noticed that local-unbound doesn't
> appear to work anymore [...]
Doug Hardie writes:
> Local unbound never worked for what I needed. [...]
Normally in a situation like this I'd just read your minds and diagnose
the issue an
> On Sep 19, 2023, at 01:37, Alain Zscheile wrote:
>
> On 2023-09-18 17:21, Chris wrote:
>
>> 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 anythi
On 2023-09-18 17:21, Chris wrote:
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).
For now, I just disabled it on
