Hello, For the record, on my system: $ aptitude why resolvconf i isc-dhcp-client Suggests resolvconf
My provider included it in their image. But this investigation is beside the point. The core issue: one package should not silently alter another package's primary behavior. Regardless of how resolvconf ended up on a system, a recursive resolver like unbound should not silently become a forwarder. 1. Installing resolvconf is not "opting in" to change unbound's behavior. 2. Users install resolvconf to manage /etc/resolv.conf, not to turn their recursive resolver into a simple forwarder. -> These are two separate intents. As for the captive portal argument: who runs Unbound locally on a laptop? And even if they did, modern systems like Fedora/KDE bind custom DNS to specific networks - connecting to a new hotspot defaults to DHCP DNS. To sum up: The current behavior shows little to no benefit while causing major issues. It breaks intended features... And breaks trust for the unbound package. I do trust you'll find the best solution as experienced dev/maintainers. I have no real preference as long as packages go back to being reliable. Thanks, LRob
