Bind and systemd-resolved

[Nick Tait]

On 1/05/2022 9:13 pm, Reindl Harald wrote:
> Am 01.05.22 um 06:38 schrieb Nick Tait via bind-users:
>> I'm not 100% sure, but I wonder if disabling systemd-resolved may 
>> create issues if, for example, you are using netplan with 
>> systemd-networkd as the renderer? E.g. Will it still be possible to 
>> pick up DNS servers from IPv6 router advertisements?
> pick up some nameservers from wherever is exactly what you *don't 
> want* in case you have named running on your machine as resolver
>
> you want 127.0.0.1 act as your resolver no matter what

Well, not always... If your local BIND service isn't a recursive 
resolver (e.g. because it is acting in a role of authoritative name 
server only), then you'd want to use a resolver on the network, which 
may be statically configured (e.g. in netplan configuration) or 
dynamically assigned (e.g. obtained from DHCP or IPv6 router 
advertisements).

I was merely offering an alternative/lower impact solution to solve the 
OP's question about how to get dig to not use 127.0.0.53 by default. It 
may not be the solution chosen by the OP (given their expressed distaste 
for systemd) but others following this thread may find it useful?

Thanks,

Nick.