Hi, On Tue, 4 Jan 2022, at 19:26, Vincent Lefevre wrote: > With resolvconf disabled, I get > > nameserver 127.0.0.1 > nameserver 10.9.0.4 > > where 127.0.0.1 is added by dhclient thanks to > > prepend domain-name-servers 127.0.0.1;
Why do you have this? This basically overrides the DHCP server by directing queries to your localhost DNS. > Concerning resolvconf: > > /run/resolvconf/resolv.conf contains the following: > > # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) > # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN > # 127.0.0.53 is the systemd-resolved stub resolver. > # run "resolvectl status" to see details about the actual nameservers. > > nameserver 127.0.0.1 > search home > > /run/resolvconf/interface/lo.unbound contains: > > nameserver 127.0.0.1 This is correct: when you run a DNS server at localhost, you don’t usually want queries to slip to the network. > I have not modified the resolvconf settings: I expect that it should > work by default. I would think this might be a bug in unbound, but since you report that the DHCP-provided DNS works when both nameserver lines are in, I think you probably don’t have unbound running, and you likely have not purged its configuration when you removed it. Localhost should not be the first entry in your resolv.conf if you want to be able to use other DNS servers. -- Cheers, Andrej
