No resolving after upgrade from Ubuntu-Secure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu-Secure-Remix |
Fix Released
|
Medium
|
YannUbuntu | ||
network-manager (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
******* PLEASE READ BEFORE POSTING:
- this particular bug applies only if you installed Ubuntu-
- this bug should concern only people who installed Ubuntu-Secure-Remix ISOs dated <04/10/2012. If you installed a newer Ubuntu-Secure-Remix ISO (downloaded after 04/10/2012), and upgrade from it, you should not get this bug.
- If you reproduce it with a recent (>04/10/2012) ISO, please create a new bug report here: https:/
******* ORIGINAL BUG REPORT:
I'm assuming (based on the prefix of /var/run/
I recently upgraded to Ubuntu 12.10 Beta 1 from a more-or-less stock installation of Ubuntu 12.04 (it had only been installed for about 3-4 hours before the upgrade). This means that I am now using network-manager 0.9.6.0-0ubuntu7. On startup, network-manager connects to my router without any issues, but I am then unable to resolve any domain names (beyond localhost); I can't browse to any websites, ping any servers using their domain names, etc. There were no problems doing any of this while using 12.04, and I did not do anything other than perform the upgrade to 12.10 Beta 1 before this happened, so what I was expecting to happen was that I would continue to be able to use DNS as usual.
On poking around a bit, I discovered that dnsmasq is running as it should be (listening on 127.0.1.1) but that the config file that it is trying to use, /var/run/
1) Kill the /usr/sbin/dnsmasq process that is automatically started (by network-manager?).
2) Manually create /var/run/
server=
3) Manually start the /usr/sbin/dnsmasq using exactly the same options that were passed to it when it was started automatically.
So, I'm guessing this file should be non-empty. (Another workaround, by the way, is to manually create an /etc/resolv.conf file with appropriate nameserver lines and then restart the networking service, but AFAIK that solution simply bypasses dnsmasq entirely.)
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: network-manager 0.9.6.0-0ubuntu7
ProcVersionSign
Uname: Linux 3.5.0-14-generic x86_64
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
Date: Sat Sep 15 13:02:05 2012
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
IpRoute:
default via 192.168.1.1 dev wlan0 proto static
169.254.0.0/16 dev wlan0 scope link metric 1000
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.21 metric 9
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to quantal on 2012-09-15 (0 days ago)
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
Wired connection 1 500ef8b0-
NotThat! 968fa0a6-
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
eth0 802-3-ethernet unavailable /org/freedeskto
wlan0 802-11-wireless connected /org/freedeskto
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running 0.9.6.0 connected enabled enabled enabled enabled disabled
summary: |
- 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 |
summary: |
- No resolving after upgrade from 12.04 to 12.10 beta + No resolving after upgrade from Ubuntu-Secure-12.04 to 12.10 beta |
Changed in network-manager (Ubuntu): | |
status: | New → Invalid |
Changed in ubuntu-secure-remix: | |
status: | New → Fix Committed |
Changed in network-manager (Ubuntu): | |
status: | Fix Committed → Invalid |
Changed in ubuntu-secure-remix: | |
assignee: | nobody → YannUbuntu (yannubuntu) |
importance: | Undecided → Medium |
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 and restarting dnsmasq is very useful to know.