Hi,

On Wed, 5 Jan 2022, at 15:17, Vincent Lefevre wrote:
> What happens with unbound is that /run/resolvconf/resolv.conf
> *always* contains "nameserver 127.0.0.1", i.e. this file never
> changes, even though the DHCP-provided nameservers (which are
> not listed in this file) do. So putting the unbound hook script
> in this /etc/resolvconf/update-libc.d directory is very silly!

Having looked at it again, it seems Thomas, the original author of resolvconf, 
have actually included a workaround for your use case.
Set TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS=no in 
/etc/default/resolvconf, and it should do the thing.

-- 
Cheers,
  Andrej

Reply via email to