I have marked this issue as affecting dnsmasq since we may want to implement a solution there along the lines of #28 or similar.
I have marked this issue as affecting resolvconf since we may want to implement a fix there along the lines of #29 or similar. (In the absence of NM and in the presence of dnsmasq, resolvconf also feeds a nameserver list to dnsmasq.) ** Summary changed: - Precise NM with "dns=dnsmasq" breaks systems with non-equivalent upstream nameservers + dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers -- 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
