Comment 9 for bug 1270189

@Jamie

I think this explains the behavior I often see when enabling WiFi and it auto-connects to a known AP. NM shows the connection as active ( ie. nmcli d ), the routing table it correct, pinging an IP address works, however for the first 30-90s after the connection comes up, DNS lookups fail. I think this is one of the underlying causes of users complaining about networking failing when they activate WiFi on Touch devices.

That said, unwinding this may be a bit tricky as NM keeps both connections active, but sets WiFi as the default route. As the DNS Servers were added in order to dnsmasq, and unwinding this in NM might be tricky, I wonder if patching this in dnsmasq is the right way to go? I'll do some investigation of dnsmasq's DBus API. If we changed dnsmasq to reverse the ordering of DNS servers. The only issue here is whether all of the DNS servers for an interface are added as group or not. If they're added individually, then reversing the order would have the effect of reversing the individual DNS servers for a particular interface too, which might not be desired behavior.