On Thu, 13 May 2021 09:41:25 -0400
Daniel J. Luke wrote:
> On May 13, 2021, at 12:14 AM, Michael B Allen <ioplex@gmail.com>
> wrote:
> > It is not completely trivial setup a caching name server. I
> > literally have two accounts so it's at least a serious nuisance.
>
> It's pretty simple to install unbound and set it up on most systems.
Actually I found "local-unbound" quite confusing on FreeBSD.
It turned-out that all you need to do is set:
local_unbound_enable=YES
local_unbound_forwarders=none
but the second line was undocumented. I had to read through 2 shell
scripts to work it out. If you miss it out unbound will get
automatically configured for forwarding on first run.
What made it doubly confusing is that it got set up with resolvconf
which I'd never given any thought to before.
Forwarding is right for almost all cases, so it wouldn't surprise me if
some Linux distributions have a similar pitfall.
Daniel J. Luke wrote:
> On May 13, 2021, at 12:14 AM, Michael B Allen <ioplex@gmail.com>
> wrote:
> > It is not completely trivial setup a caching name server. I
> > literally have two accounts so it's at least a serious nuisance.
>
> It's pretty simple to install unbound and set it up on most systems.
Actually I found "local-unbound" quite confusing on FreeBSD.
It turned-out that all you need to do is set:
local_unbound_enable=YES
local_unbound_forwarders=none
but the second line was undocumented. I had to read through 2 shell
scripts to work it out. If you miss it out unbound will get
automatically configured for forwarding on first run.
What made it doubly confusing is that it got set up with resolvconf
which I'd never given any thought to before.
Forwarding is right for almost all cases, so it wouldn't surprise me if
some Linux distributions have a similar pitfall.