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
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
