Hi again, On Wed, 5 Jan 2022, at 09:56, Andrej Shadura wrote: > In fact, unbound comes with resolvconf integration, so it should know > about other nameservers coming from DHCP. It is likely that the fact > you add 127.0.0.1 in front of them is preventing that integration from > working properly. Or maybe it’s a bug.
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. -- Cheers, Andrej
