On 2022-01-05 10:04:38 +0100, Andrej Shadura wrote: > I just wanted to clarify: unbound already puts itself (as 127.0.0.1) > first in resolvconf configuration. You should not need to modify you > DHCP client’s configuration to add it once more. Unbound’s > resolvconf integration should theoretically filter 127.0.0.1 out and > tell unbound to forward its requests to your network’s name servers, > but for some reason it doesn’t. Or maybe you’ve modified unbound’s > configuration to disallow that.
After testing, /etc/resolvconf/update.d/unbound isn't run at all: I've added "logger /etc/resolvconf/update.d/unbound" at the beginning of this script, and it doesn't appear in the logs. So this seems to be a resolvconf bug. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
