Public bug reported:
My computer happens to be connected to two networks through eth0 and
wlan0. NetworkManager connects to both of them automatically and use
DHCP for both of them. Both networks are protected from the outside by
firewalls and they are lots of DNS servers (obtained automatically).
Since the upgrade to Precise, DNS no longer works without manual
intervention.
What happens is that, since bug #903854, dnsmasq no longer receives the
option --strict-order. As a consequence, it tries servers in a random
order to resolve DNS requests. In particular, it tries to access DNS
servers from the wireless network through the eth0 route, which crosses
a firewall, and therefore it fails to resolve requests. It takes a lot
of failures before all the unreachable servers have been exhausted,
which makes for a poor user experience.
With the --strict-order option, dnsmasq tries to access servers that can
be accessed by the default route, which succeeds immediately. Note that
I am not sure that --strict-order is the proper fix and it may only be
papering over a real bug, but at least it does fix the issue.
network-manager: 0.9.4.0-0ubuntu2
dnsmasq-base: 2.59-4
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
--
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/979067
Title:
Please reenable dnsmasq --strict-order
Status in “network-manager” package in Ubuntu:
New
Bug description:
My computer happens to be connected to two networks through eth0 and
wlan0. NetworkManager connects to both of them automatically and use
DHCP for both of them. Both networks are protected from the outside by
firewalls and they are lots of DNS servers (obtained automatically).
Since the upgrade to Precise, DNS no longer works without manual
intervention.
What happens is that, since bug #903854, dnsmasq no longer receives
the option --strict-order. As a consequence, it tries servers in a
random order to resolve DNS requests. In particular, it tries to
access DNS servers from the wireless network through the eth0 route,
which crosses a firewall, and therefore it fails to resolve requests.
It takes a lot of failures before all the unreachable servers have
been exhausted, which makes for a poor user experience.
With the --strict-order option, dnsmasq tries to access servers that
can be accessed by the default route, which succeeds immediately. Note
that I am not sure that --strict-order is the proper fix and it may
only be papering over a real bug, but at least it does fix the issue.
network-manager: 0.9.4.0-0ubuntu2
dnsmasq-base: 2.59-4
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/979067/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
