For Debain unstable with also systemd-resolved enabled I needed these:<p>&#x2F;etc&#x2F;dnsmasq.d&#x2F;network-manager:<p>bind-interfaces<p>interface=lo<p>&#x2F;etc&#x2F;systemd&#x2F;resolved.conf:<p>[Resolve]<p>DNS=127.0.0.1 ::1<p>&#x2F;etc&#x2F;nsswitch.conf:<p>passwd:         compat<p>group:          compat<p>shadow:         compat<p>hosts:          files mymachines gw_name myhostname mdns4_minimal resolve [NOTFOUND=return] dns mdns4<p>networks:       files<p>protocols:      db files<p>services:       db files<p>ethers:         db files<p>rpc:            db files<p>netgroup:       nis<p>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&#x27;s going to query dnsmasq directly instead of first resolved (which is also using dnsmasq anyway).