Hello, > 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. That is, names cannot be resolved anymore. Though this is not a big problem when no other package is installed in the same "apt-get install" or so, it must be considered that maybe other packages needing network access for configuration are installed in the same apt-get run. So, the executable REALLY should be set before unbound is started for the first time. Regards Christoph
