Package: dnsmasq Severity: normal In some networks the nameservers are non-equivalent: some can resolve private domain names and some can't. The addresses of the former are listed earlier than the addresses of the later in, e.g., DHCP results. Dnsmasq, however, normally assumes that all nameservers are equivalent and chooses the fastest one; so if a nonhomogeneous list of nameservers is sent to dnsmasq, it could occur that the latter systematically fails to resolve private names.
This problem can be addressed by making the dnsmasq binary smarter as is being discussed in Launchpad issue #1003842. Another possibility is to change the resolvconf hook script such that it causes dnsmasq to switch to strict-order mode if the list includes private IP addresses. Alternatively, to change the hook script such that it truncates the list after the first private IP address. Of course, this only addresses the case where resolvconf is also installed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
