As a "quick" fix, it might be possible to just include the DNS servers
reported by DHCP twice for dnsmasq: once by itself for "global"
resolution, and once with the search domain from DHCP so that local
network resolution might work. I'll investigate the idea, as that would
likely solve at least half of the problem cases here.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => In Progress
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: network-manager (Ubuntu Precise)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: network-manager (Ubuntu Precise)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
