Please note that bug 1666318 has relevant information. It appears that editing
/etc/NetworkManager/NetworkManager.conf
and removing "dns=dnsmasq" makes the problem go away.
So, this could be a bug in either network manager or in dnsmasq
Please note that bug 1666318 has relevant information. It appears that editing
/etc/NetworkMan ager/NetworkMan ager.conf
and removing "dns=dnsmasq" makes the problem go away.
So, this could be a bug in either network manager or in dnsmasq