** Changed in: dnsmasq (Ubuntu) Status: New => Triaged ** Changed in: dnsmasq (Ubuntu Precise) Status: New => Triaged
** Changed in: network-manager (Ubuntu) Status: New => Invalid ** Changed in: network-manager (Ubuntu Precise) Status: New => Invalid ** Summary changed: - SDFEEWRDSsdfdasfsdf + dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers ** Tags added: precise xenial ** Description changed: - dfasfwerwq2323sf + 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 8.8.8.8 + + 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=8.8.8.8 + + 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 8.8.8.8. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs