Christoph Pleger wrote: > > The resolvconf update.d hook for unbound is somewhat problematic, so it > > is disabled by default. Enabling or disabling a resolvconf update.d hook > > is done by setting or clearing the executable bit on the hook. > > But when the executable bit is not set and resolvconf is installed, the > user ends up with no usable nameserver configuration after installation of > unbound, because resolv.conf only contains 127.0.0.1 (for the local > unbound) as nameserver entry and without further configuration unbound > does not know how to resolve names.
Yes, it does? In the default configuration Unbound performs recursion to resolve names. -- Robert Edmonds [email protected]
