I just did a fresh install on 2 laptops that were working fine with version 12.04. Both laptops have this issue with version 12.10. I've tried commenting out dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf and creating a wrapper script for dnsmasq that removes the --no-hosts option. Neither of these suggestions worked and the wrapper script caused the system startup to hang.
I've read comments that the dnsmasq functionality has been part of Network Manager since version 12.04; however, I didn't see this problem on 12.04. It seems that something changed with 12.10 to manifest it. I'm surprised that I haven't seen more reports of it. It also seems odd that some are reporting that the work arounds worked and others are not reporting the problem at all. I agree with another poster that this bug should be marked critical. It's very annoying that such a basic and critical OS functionality was broken and the bug is only marked as Opinion and remains unassigned. I held off on installing 12.10 to allow time for bug fixes but, sadly, I didn't wait long enough. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/993298 Title: Please make NetworkManager-controlled dnsmasq respect /etc/hosts Status in “network-manager” package in Ubuntu: Opinion Bug description: 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 [1] 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/NetworkManager/NetworkManager.conf and comment the 'dns=dnsmasq' line then do a 'sudo restart network-manager'." 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 [3]? 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. [1] http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/src/dnsmasq-manager/nm-dnsmasq-manager.c, line 285 [2] i.e. http://ubuntuforums.org/showthread.php?t=1968061 [3] http://www.stgraber.org/2012/02/24/dns-in-ubuntu-12-04/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/993298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
