unbound-control in FreeBSD-CURRENT and stable/10

Ilya Bakulin webmaster at kibab.com
Mon Dec 2 12:56:59 UTC 2013


On 2013-11-29 20:26, Darren Pilgrim wrote:
> On 11/29/2013 6:27 AM, Ilya Bakulin wrote:
> 
> There's really no bug to fix.  The base has unbound in it,
> unbound-control is part of unbound.  If you install unbound from
> ports, you should delete unbound from base.  I haven't tried out 10.x
> yet, but you usually just set a knob like WITHOUT_UNBOUND in
> /etc/src.conf, then do:
Why on earth I should rebuild the whole system just to get rid of 
Unbound? Actually Unbound in base should be used only as a DNSSEC-aware 
resolver for the localhost, not as "real" DNS server. Just like BIND 
used to be earlier. You haven't recompiled the system (and lost 
freebsd-update!) when installing BIND from ports, have you?

> Change your PATH to have /usr/local/bin and /usr/local/sbin first.
> The shell will find /usr/local/bin/unbound-control first and run that.
>  I recommend this in general, since you pretty much always want a name
> collision to prefer the from-ports program.

This sounds a lot better, although then I don't understand why the 
system is not shipped with this setting by default.



More information about the freebsd-hackers mailing list