Configs looks correct. Are you trying to resolve something on the
internal network or on the Internet?
The one thing I can think of is that 127.0.0.1 is listed in
/etc/resolv.conf which shouldn't happen if dnsmasq isn't running -- and
dnsmasq doesn't appear to be enabled in NetworkManager.conf; so maybe
it's running and configured externally, in which case you'll want to
revise the dnsmasq configuration in /etc.
On the other hand, if you have only just removed the dns=dnsmasq line
from /etc/resolv.conf; you will need to reboot or restart network-
manager for the changes to take effect.
I'm seeing the following in the attached syslog:
Jun 6 16:53:26 b20223-02 NetworkManager[3353]: <warn> dnsmasq exited with
error: Network access problem (address in use; permissions; etc) (2)
This indicates that NM is trying to start dnsmasq (which only can happen
if dns=dnsmasq is set), but something is interfering: either another
dnsmasq instance, or a running instance of bind or another resolver
daemon.
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009392
Title:
dns lookup failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1009392/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
