Maintained by: NLnet Labs

[Unbound-users] error when threading enabled on local_unbound on FreeBSD 10.x

unbound at fongaboo.com
Mon Jul 20 23:47:35 CEST 2015


Thanks,

I am now attempting to install from ports. However, am I gathering 
correctly that FreeBSD's local_unbound's config files live in /etc/unbound 
while stock unbound has them in /usr/local/etc/unbound?

When I run unbound-control-setup, it seems to put the files it generates 
in /etc/unbound anyway. What do I have to do to make sure everything 
defaults to the stock setup instead of the local_unbound setup?



On Mon, 20 Jul 2015, Mathieu Arnold wrote:

>
>
> +--On 20 juillet 2015 10:30:20 +0200 Jaap Akkerhuis <jaap at NLnetLabs.nl>
> wrote:
> |  lst_hoe02 at kwsoft.de writes:
> |
> |  >
> |  >
> |  > Zitat von unbound at fongaboo.com:
> |  >
> |  > > I was setting up local_unbound (the built-in instance of unbound in
> |  > > FreeBSD 10.x). However, I had a conf file that I had a much more
> |  > > customized from a previous install of the stock unbound I had on
> |  > > earlier box.
> |  > >
> |  > > When I tried to transplant the more elaborate conf and have
> |  > > local_unbound run it, I got the following errors:
> |
> | This is a FreeBSD issue. The local_unbound thingy is configured
> | just for running a local resolver/cache. If you want to run a full
> | blown unbound resolver which should serve also other machines on
> | you network, you are better off with disbaling the local_unboun and
> | install & run the one from the ports.
>
> +1, there is a good reason the local_unbound config file is hidden some
> place *not* in /etc, and automatically generated.  It s because you DO NOT
> touch it.  It is to be used as a local resolver only.  If you want to use
> unbound for something else, you install it from ports.
>
> -- 
> Mathieu Arnold