The problem could be simply that the symbolic link at /etc/resolv.conf
is missing. This should be a symbolic link with value
"../run/resolvconf/resolv.conf". Create it by doing
ln -nsf ../run/resolvconf/resolv.conf /etc/resolv.conf
and then rebooting. After rebooting do the following in a t
I'm sorry, but it is now looking like what I posted as the first
"workaround" -- adding server addressed into /var/run/nm-dns-
dnsmasq.conf -- does not actually work. It turned out that I still had a
manually-created /etc/resolv.conf file present on my system when I was
using that "solution." Once
** Attachment added: "interfaces"
https://bugs.launchpad.net/bugs/1051348/+attachment/3316908/+files/interfaces
--
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/1051348
Title:
NM no longer uses nm-dns-dnsmasq.conf to tell nm-dnsmasq its forwarding
addresses. NM now uses D-BUS for that purpose. So that's not the
problem.
That you have no domain name service is obviously a problem.
That you could restore service by sticking nameserver addresses into nm-
dns-dnsmasq.conf
** Summary changed:
- No DNS resolution after upgrade from 12.04 to 12.10 beta,
/var/run/nm-dns-dnsmasq.conf empty
+ No DNS resolution after upgrade from 12.04 to 12.10 beta
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manage
5 matches
Mail list logo
