Comment 1 for bug 979067

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote : Re: Please reenable dnsmasq --strict-order

Seems to me like this is possibly not the exact cause of the issue. It's expected that any network reachable via the default route (when no "more specific" route exists) will be attempted via the default route (because the kernel is supposed to always use the most specific route to get to a destination).

Furthermore, dnsmasq is supposed to be trying the dns nameservers in parallel, or at least sufficiently quickly and without blocking that this shouldn't affect network resolution in a bad way.

Could you please attach the contents of /run/nm-dns-dnsmasq.conf as well as the output of 'ip route' when you are reproducing the issue so that we can debug this?