On 2021/11/08 15:50, Klemens Nanni wrote: > With this diff pppoe(4) sends two nameservers and thus wins, but that is > expected and setups such as mine must either > - disable resolvd > - enable resolvd but also enable unwind > (unwind also learns DNS proposals but always wins in resolv.conf) > - enable resolvd and clear pppoe(4) proposals, > e.g. `route nameserver pppoe0' > - do whatever else fits their setup
This is already a problem though having additional sources of nameserver addresses does mean that more people will run into it. Most resolvers handed out by ISPs or on local networks are only reachable from (or at least only give valid responses to) IPs on the expected network; that's OK when the nameserver is in the same subnet as the client (typical home ISP router config) but otherwise it's not (you do get to learn how very quick resolvd is at changing the file back to what it wants though!). Feels like maybe it should only add a resolver if it's either on a directly-connected interface or there's a route for the ns address pointing at the interface that the ns was learned from. Though there's an extra complication if you have multiple route tables..
