while this also happens in Debian, the use case is more common in Ubuntu, because NetworkManager is patched to use a spawned dnsmasq instance as a local resolver, and mixing the two DNS servers is problematic (neither bind-dynamic nor bind-interfaces work very well).
In Debian they more frequently use the normal dnsmasq/DNS service as it was designed, because NM doesn't spawn a local resolver there.
For upstream report, Simon (the upstream dnsmasq developer and Debian maintainer) already answered here, Simon would you like me to file a debian bug as well? It's easy to work around this issue, so we can even close it with won't fix if you prefer.
Hi Robie,
while this also happens in Debian, the use case is more common in Ubuntu, because NetworkManager is patched to use a spawned dnsmasq instance as a local resolver, and mixing the two DNS servers is problematic (neither bind-dynamic nor bind-interfaces work very well).
In Debian they more frequently use the normal dnsmasq/DNS service as it was designed, because NM doesn't spawn a local resolver there.
For upstream report, Simon (the upstream dnsmasq developer and Debian maintainer) already answered here, Simon would you like me to file a debian bug as well? It's easy to work around this issue, so we can even close it with won't fix if you prefer.
Thank you.