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: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
** Changed in: dnsmasq (Ubuntu Precise)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
