3 ms·
For Debain unstable with also systemd-resolved enabled I needed these: /etc/dnsmasq.d/network-manager: bind-interfaces interface=lo /etc/systemd/resolved.co
by Klasiaster 11y ago
For Debain unstable with also systemd-resolved enabled I needed these:
/etc/dnsmasq.d/network-manager:
bind-interfaces
interface=lo
/etc/systemd/resolved.conf:
[Resolve]
DNS=127.0.0.1 ::1
/etc/nsswitch.conf:
passwd: compat
group: compat
shadow: compat
hosts: files mymachines gw_name myhostname mdns4_minimal resolve [NOTFOUND=return] dns mdns4
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
They are so many as I also have the packages libnss-myhostname libnss-mymachines libnss-gw-name libnss-mdns. Important to note is the NOTFOUND=return directive after resolve, because libnss-resolved is not available on Debian yet and thus it's going to query dnsmasq directly instead of first resolved (which is also using dnsmasq anyway).