This bug was fixed in the package network-manager -
0.9.2.0+git201202161854.8572ecf-0ubuntu4
---------------
network-manager (0.9.2.0+git201202161854.8572ecf-0ubuntu4) precise; urgency=low
[ Gabor Kelemen ]
* debian/network-manager.upstart: Make NM aware of the locale. (LP: #875017)
[ Mathieu Trudel-Lapierre ]
* debian/patches/lp936712_dnsmasq_ip6_ns_ordering.patch: order IPv6
nameservers before IPv4 ones in dnsmasq config: dnsmasq is able to properly
deal with broken IPv6 nameservers (or routers). (LP: #936712)
* debian/control: add Conflicts: connman to network-manager. (LP: #659460)
* debian/patches/manage-privacy-extensions.patch: set the default for using
IPv6 Privacy extensions to TRUE; this is just correcting an oversight from
adapting the upstream patch. (LP: #176125)
-- Mathieu Trudel-Lapierre <[email protected]> Tue, 21 Feb 2012 19:40:35
-0500
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/936712
Title:
NetworkManager should put IPv6 DNS servers before IPv4 DNS servers in
dnsmasq configuration (and possibly resolv.conf)
Status in “network-manager” package in Ubuntu:
Fix Released
Bug description:
In cases where you are indeed on a dual-stack network and received DNS
information from either SLAAC or DHCPv6, these should be used before
any equivalent IPv4 data (usually a fallback/compatibility layer in
such environment).
As an example, here's my generated /run/nm-dns-dnsmasq.conf on an up to date
12.04 system:
server=172.17.20.30
server=172.17.25.30
server=172.16.20.32
server=2001:470:c364:1020:e084:d1ff:fe38:c4f5
server=2001:470:c364:1025:8837:98ff:fe43:90e6
server=2001:470:b4e9:1020:218:51ff:fe5a:9949
The result is that dnsmasq will only use the IPv6 dns servers if all 3 IPv4
dns servers are marked as failed.
As dnsmasq is perfectly able to detect and avoid broken DNS servers,
favoritizing IPv6 servers shouldn't cause any damage even in
environment where the information received by NM is wrong.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/936712/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
