Re:dhcpleased(8) and resolvd(8) enabled in base, replacing d...
by tedunangst on Saturday July 17, 2021 @09:24PM
(#27870117)
I think the current path of least resistance would be unwind with unwind.conf forwarding to unbound.
Re:dhcpleased(8) and resolvd(8) enabled in base, replacing d...
by daneel_w on Saturday July 17, 2021 @09:40PM
(#27870175)
Yes. Clumsy. It's an unusually awkward design choice to have the software detect if another specific application is running in order to trigger the behavior, instead of just giving the user the ability to configure it.
In my opinion this whole new dhcpleased/resolvd setup is poorly planned, as it contrives the gruesome trick of being both a privacy/integrity problem (no user control over ISP DNS making its way into resolv.conf) and a userland villainy problem (forcefully altering behavior based on whether some other application is running, no matter what the user's actual intention is for running that application).
Since I don't involve Unwind here, which according to the manpages of the new daemons is what makes them prepend "127.0.0.1" to resolv.conf, and since I cannot see any apparent way of configuring the new daemons to ignore DNS information in the DHCP response the way I can with dhclient, how can I achieve what I have now? How can I prevent my ISP's DNSes from entering resolv.conf when running the new daemons?
I get the impression that my use case (which really is neither uncommon nor obscure) hasn't been thought of at all.