I'm on Ubuntu 14.04. This is affecting me. I'm sharing my wifi connection. The problem is that there's a server that has to be queried from a DNS outside of my normal one, but since dnsmasq is using default DNS servers set by dhcp, the devices behind this shared wifi connection can't connect to that specific server. I need to add a line to dnsmasq configuration, such as server=/this.specific.server/specific.dns.ip I found no way to do it and even trying to send a message with dbus did not work (for me). Probably I could not sort it out.
I have the specific server ip hardcoded in the /etc/hosts file. If dnsmasq respected the /etc/hosts file, then the hosts behind the shared wifi connection could have obtained the right ip address for the server. It's very strange to hardcode dnsmasq parameters into the C code rather than leaving it out to some configuration file. -- 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: Confirmed 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
