This breaks domain name resolution in Ubuntu 16.04, as seen in bug #1522057.
tags: added: precise xenial Changed in network-manager (Ubuntu): importance: Medium → Critical Changed in dnsmasq (Ubuntu Precise): importance: Medium → Critical Changed in dnsmasq (Ubuntu): importance: Medium → Critical Changed in network-manager (Ubuntu Precise): importance: Medium → Critical Changed in network-manager (Ubuntu): status: Confirmed → Invalid Changed in network-manager (Ubuntu Precise): status: Triaged → Invalid Changed in dnsmasq (Ubuntu): status: Confirmed → Triaged Changed in dnsmasq (Ubuntu Precise): status: Confirmed → Triaged ** Changed in: dnsmasq (Ubuntu) Assignee: sunil (chikkalli) => nikhil (nikhilnikki) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers Status in dnsmasq package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Invalid Status in dnsmasq source package in Precise: Triaged Status in network-manager source package in Precise: Invalid Status in dnsmasq package in Debian: New Bug description: A number of reports already filed against network-manager seem to reflect this problem, but to make things very clear I am opening a new report. Where appropriate I will mark other reports as duplicates of this one. Consider a pre-Precise system with the following /etc/resolv.conf: nameserver 192.168.0.1 nameserver 22.214.171.124 The first address is the address of a nameserver on the LAN that can resolve both private and public domain names. The second address is the address of a nameserver on the Internet that can resolve only public names. This setup works fine because the GNU resolver always tries the first- listed address first. Now the administrator upgrades to Precise and instead of writing the above to resolv.conf, NetworkManager writes server=192.168.0.1 server=126.96.36.199 to /var/run/nm-dns-dnsmasq.conf and "nameserver 127.0.0.1" to resolv.conf. Resolution of private domain names is now broken because dnsmasq treats the two upstream nameservers as equals and uses the faster one, which could be 188.8.131.52. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : email@example.com Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp