Please make NetworkManager-controlled dnsmasq respect /etc/hosts
Since 12.04 NetworkManager uses the dnsmasq plugin by default to resolve DNS requests. Unfortunately the dnsmasq plug-in has --no-hosts, etc. hard coded  which means (among other things) that after the upgrade to 12.04 /etc/hosts will no longer be used to resolve DNS requests. This changes the prior behavior of NetworkManager without any visible warning to the end user. AFAICS there's no other way to work around this problem as to manually revert the change and disable the dnsmasq plug-in in the NetworkManager config, see [2,3]:
"To turn off dnsmasq in Network Manager, you need to edit /etc/NetworkMan
This is of course not a bug in the NetworkManager which just behaves as intended. The problem is in the change of the configuration of the Ubuntu packaging which will probably leave many wondering why their /etc/hosts suddenly no longer works. This cost me considerable time to debug and probably is a usability problem for others, too.
Maybe you could provide a more visible documentation than that in ? E.g., *including a comment in /etc/hosts that explains the change* and how to work around it would have saved me a lot of time. It would have automatically alerted me on upgrade as manual changes to /etc/hosts would then have triggered a prompt while leaving those users with standard /etc/hosts in peace.
Probably similar problems arise with other disabled config files and could be alerted to the users? Thinking of resolv.conf, etc.
 i.e. http://
- NetworkManager does not use local hosts configuration any more
+ NetworkManager-controlled dnsmasq does not respect /etc/hosts
|karloskar (karloskarmattsson) wrote : Re: NetworkManager-controlled dnsmasq does not respect /etc/hosts||#4|
- NetworkManager-controlled dnsmasq does not respect /etc/hosts
+ Please make NetworkManager-controlled dnsmasq respect /etc/hosts
|Changed in network-manager (Ubuntu):|
|status:||Opinion → Confirmed|