In the same bug report we discuss various ways of getting NetworkManager-controlled dnsmasq ("nm-dnsmasq") and standalone dnsmasq to coexist. The best solution we've found so far also entails forcing standalone dnsmasq into bind-interfaces mode; beyond that it entails changing nm-dnsmasq's listen address to 127.0.0.2. Again, once dnsmasq is enhanced the inconveniences of bind-interfaces mode should be largely eliminated.
(Cont'd.) Simon Kelley on enhancing dnsmasq and subsequent discussion in bug #959037 comment #89 (e.g.).
https:/ /bugs.launchpad .net/ubuntu/ +source/ dnsmasq/ +bug/959037/ comments/ 89
In the same bug report we discuss various ways of getting NetworkManager- controlled dnsmasq ("nm-dnsmasq") and standalone dnsmasq to coexist. The best solution we've found so far also entails forcing standalone dnsmasq into bind-interfaces mode; beyond that it entails changing nm-dnsmasq's listen address to 127.0.0.2. Again, once dnsmasq is enhanced the inconveniences of bind-interfaces mode should be largely eliminated.