to 12.6.2025 klo 8.17 Martin-Éric Racine (martin-eric.rac...@iki.fi) kirjoitti: > > to 12.6.2025 klo 6.05 Russell Coker (russ...@coker.com.au) kirjoitti: > > > > Package: dhcpcd > > Version: 1:10.1.0-11 > > Severity: normal > > > > I connect to a network and immediately run "resolvectl" and see the > > following: > > > > Link 3 (wifi) > > Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 > > Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS > > DNSSEC=no/unsupported > > Current DNS Server: 192.168.0.17 > > DNS Servers: 192.168.0.17 > > DNS Domain: REDACTED > > Default Route: yes > > > > I run it again a couple of seconds later and that is gone. I add it again > > manually with the command "resolvectl dns wifi 192.168.0.17" and it is good > > for a second or two and then goes away again. The only way I can keep it > > going is using watch(1) to repeatedly run resolvectl to keep adding it back > > as dhcpcd keeps removing it. It was not obvious that dhcpcd was doing this > > in the background. Also it doesn't happen on all networks for unknown > > reasons, it seems to happen with isc-dhcp-server but not with kea but I have > > a small sample size. > > > > dhcpcd should do at least one of the following: > > > > 1) Take the same DNS data from dhcp as network-manager and use the same > > settings. > > 2) Realise that something else configured an interface and do nothing with > > it. > > 3) Not be run by default on all interfaces. > > dhcpcd-base does nothing by itself. It has to be triggered by a line > in /etc/network/interfaces, and network-manager knows how to skip > interfaces that are mentioned there.
I just realized that you meant bin:dhcpcd. See the package description. bin:dhcpcd is not meant to be installed on hosts where network-manager or some other tool will configure the network. Meanwhile, bin:dhcpcd-base (which comes on a default Trixie install) does nothing by itself. It needs a 'dhcp' stanza in /etc/network/interfaces to have bin:ifupdown call it for specific interfaces. Martin-Éric
