Hi Simon.
Before I forget to ask: can you please update dnsmasq(8) to include
under "--strict-order" a description of what happens when nameserver
addresses are passed in via D-Bus instead of via a file?
You wrote,
> you can very easily provide the same behaviour - only pass the first
> nameserver to dnsmasq
Because NM doesn't use dnsmasq to cache, if NM were to give dnsmasq only
one address then I guess the only service that dnsmasq would still
provide is that of name-to-server mapping.
And it turns out that the way NM currently uses dnsmasq to do this is
seriously flawed. So I conclude that it's better for NM not to use
dnsmasq at all until these problems are solved.
> [That NM only supplies one nameserver address per domain name]
> is a different problem, and could be solved.
>From the man page it's not completely clear how to solve it. Can you
confirm (1) that it's possible to give multiple server options as
follows
server=/google.com/1.2.3.4
server=/google.com/5.6.7.8
and that the result will be that 1.2.3.4 and 5.6.7.8 will be treated
equally for the purpose of resolving names in domain google.com? (2) And
likewise via D-Bus?
(3) What effect does strict-order have on this?
> Ironically, I think the
> problem arises because for nameservers associated with particular
> domains, the equivalent of --strict-order is always in play.
What you say here suggests that my proposition #1 above is false. If #1
is false then it seems that in order to fix
--
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:
dnsmasq sometimes fails to resolve private names in networks with non-
equivalent nameservers
Status in “dnsmasq” package in Ubuntu:
Confirmed
Status in “network-manager” package in Ubuntu:
In Progress
Status in “dnsmasq” source package in Precise:
Confirmed
Status in “network-manager” source package in Precise:
Triaged
Status in “dnsmasq” package in Debian:
New
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/dnsmasq/+bug/1003842/+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
