To simon, in #14.

> Question: does networkmanager's GUI expose the option to divert particular 
> domains to a special nameserver? That's an
> alternative correct way to achieve layering local names over the global DNS.

IMHO, this cannot be use to solve all the current problems. The issue
came out because many, many network access authorization portals are
intranet hosts which can be resolved only by the intranet nameserver.
There are tons of these around the world and everybody who goes around
with a laptop encounters them all the time.  When you get to an
authorization portal, you may not know what the domain is.  You only
know what dhcp tells you.

So, either you implement some smart heuristics (e.g., if the first
nameserver is on an intranet ip address, try that sequentially), or you
stop trusting an authoritative "I do not know that host" and require a
confirmation, or you use the sequential access that is typical of the
resolv library and of MS windows, because in the context of
authorization portals, non-equivalent servers exist and we have little
power to change this as long as they work with MS windows and the MAC,
so IMHO we need to workaround.

It is unfortunate, but having a "sane" or "insane" behavior in some
linux distro will anyway have negligible effect on the spread of non-
equivalent servers. It will not discourage or encourage the use of non-
equivalent servers, as most people will anyway take what OSes that have
majority market share as the de facto standard and only test against
that.

-- 
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/1003842

Title:
  Precise NM with "dns=dnsmasq" breaks systems with non-equivalent
  upstream nameservers

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  A number of reports already filed against network-manager seem to
  reflect this problem, but to make things very clear I am opening a new
  report.  Where appropriate I will mark other reports as duplicates of
  this one.

  Consider a pre-Precise system with the following /etc/resolv.conf:

      nameserver 192.168.0.1
      nameserver 8.8.8.8

  The first address is the address of a nameserver on the LAN that can
  resolve both private and public domain names.  The second address is
  the address of a nameserver on the Internet that can resolve only
  public names.

  This setup works fine because the GNU resolver always tries the first-
  listed address first.

  Now the administrator upgrades to Precise and instead of writing the
  above to resolv.conf, NetworkManager writes

      server=192.168.0.1
      server=8.8.8.8

  to /var/run/nm-dns-dnsmasq.conf and "nameserver 127.0.0.1" to
  resolv.conf.  Resolution of private domain names is now broken because
  dnsmasq treats the two upstream nameservers as equals and uses the
  faster one, which could be 8.8.8.8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1003842/+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

Reply via email to