> In my network dnsmasq should not try to connect directly
> to the DNS root servers(which it looks like it does),
It doesn't. Dnsmasq only ever forwards DNS requests to other nameservers which
can do iterative queries.
> But there is nothing telling it to use them, since both
> /var/run/nm-dns-dnsmasq.conf and
> /etc/NetworkManager/dnsmasq.d (which dnsmasq
> is set to use when started by network-manager)
> are empty.
You can't go by those files. In Quantal, NM sends nameserver addresses to
dnsmasq via D-Bus.
How to see what NM has told dnsmasq:
nmcli -f IP4 dev list | grep DNS
> but resolvconf just won't use them, since it keeps
> getting localhost from /run/resolvconf/interface/lo.dnsmasq.
The latter file is created by the standalone dnsmasq server. When the
latter is started with its initscript, the initscript registers the
address 127.0.0.1 with resolvconf. If all is well then the standalone
dnsmasq server instance uses the NM-controlled dnsmasq instance as its
sole upstream nameserver, but perhaps this isn't happening in your case
because of some some misconfiguration.
If you don't want to use the standalone dnsmasq server then it's best to
purge the "dnsmasq" package. Leave the "dnsmasq-base" package installed:
it includes the dnsmasq binary which is used both by NetworkManager and
by the "dnsmasq" package.
** Project changed: network-manager => network-manager (Ubuntu)
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
** Tags added: quantal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1083111
Title:
network-manager doesn't configure DNS properly and name resolution
fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1083111/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
