On 2022-01-04 19:04:46 +0100, Andrej Shadura wrote: > Thanks for the bug report. Can you please provide more information? > Similar setups elsewhere work and use the nameservers provided by > DHCP, I’m not sure why this one wouldn’t.
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; in its /etc/dhcp/dhclient.conf configuration file. So I suppose that "nameserver 10.9.0.4" comes from the DHCP server, which would make sense as I get $ route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 10.9.0.4 0.0.0.0 UG 600 0 0 wlp61s0 10.9.0.0 0.0.0.0 255.255.240.0 U 600 0 0 wlp61s0 link-local 0.0.0.0 255.255.0.0 U 1000 0 0 wlp61s0 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 I have not modified the resolvconf settings: I expect that it should work by default. -- 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)
