On 21/04/2025 06:04, Martin-Éric Racine wrote: > Hey Ken, > > > Thanks for this bug report and very thorough analysis. > > Can you submit a report upstream and link to this bug? > > https://github.com/NetworkConfiguration/dhcpcd/issues/new > > Martin-Éric
I have done so: https://github.com/NetworkConfiguration/dhcpcd/issues/500 Please note, however, that I don't really think this is a defect upstream: IMHO it is really a distribution integration issue which should be solved within Debian: - dhcpcd provides resolvconf integration, but it doesn't claim to support the crippled systemd version of resolvconf. Indeed, the same maintainer distributes openresolv for this very purpose! - systemd provides their stand-in version of resolvconf, but it is specifically documented that it is only a "limited resolvconf compatibility mode" and "Not all operations supported by other implementations are supported natively". See: https://manpages.debian.org/testing/systemd-resolved/resolvectl.1.en.html - Dealing with multiple different sources of name server information requires co-operation between different packages, either by using the "proper" resolvconf, or the scripting hacks mentioned above which are shared by ifupdown and isc-dhcp-client, or some other mechanism. Any fix specific to dhcpcd will only ever be a partial solution.
