I'd like to point out that the description of the bug is inaccurate.
When networkmanager uses dnsmasq, resolv.conf should not be updated when
new dns servers must be used. Instead, networkmanager needs to update
dnsmasq's configuration. And it does not do that, which is a problem.
Proper
I can confirm that this bug does not occur when you disable dnsmasq for
NetworkManager.
However, I wanted to add how you can do so:
Open /etc/NetworkManager/NetworkManager.conf in an editor and change
dns=dnsmasq
to this:
#dns=dnsmasq
Then, restart NetworkManager:
sudo service network-manager
2 matches
Mail list logo