On 30/09/2026 06:36, Martin-Éric Racine wrote: > > Have we reached a conclusion on this particular issue? > > Martin-Éric
The position I came to personally at the time was that various compromises could be reached if it were made possible to install resolvconf (or openresolv) and systemd-resolved together on a Debian system and configure them to coexist as needed. The only hard barrier to this is that the systemd-resolved package insists on installing a symbolic link to its resolvectl utility from /usr/sbin/resolvconf, and this forces it into conflict with the resolvconf package (and by extension with opennresolv). The irony here is that the systemd "replacement" for resolvconf is not really a replacement. It fails to replicate the full functionality of either openresolv or resolvconf, and I'd be surprised if anyone is using it in anger. So the symlink in question would be better handled as an optional extra, maybe in a separate trivial package. With resolvconf and systemd-resolved both installed, various different setups might be possible, depending on admin requirements, e.g: - The libnss-resolve NSS plugin could be disabled, and DNS lookups routed through resolvconf in the traditional way. Per-interface DNS addresses from systemd-resolved (obtained from systemd-networkd, usually from a DHCP server) could be fed into resolvconf just as it is now from other systems such as NetworkManager. This approach would suit a server system where the admin wants to control the source of DNS information in the traditional way, but also wants to be able to configure interfaces automatically with systemd-networkd, and use any DNS server addresses coming out of DHCP. - resolvconf could be configured not to write resolv.conf directly, but make the DNS addresses available to systemd-resolved as global nameservers. Name resolution would be through libnss-resolve and the resolved DNS server as configured. This approach is probably less useful than that above, but would suit someone who wants to make use of the resolved DNS cache while at the same time injecting DNS server information from other packages which are already integrated with resolvconf. I raised a bug [1] with systemd-resolved to try and explain the above, but it hasn't received any attention AFAICT. - Ken. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103785
