transient dns errors

[Erno Kuusela]

I have been getting random "site not found" errors when web browsing on the campus network and these seem to be cured by disabling the dnsmasq config used by NetworkManager.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.4.0-0ubuntu4.2
Uname: Linux 3.8.0-030800rc2-generic x86_64
ApportVersion: 2.0.1-0ubuntu15.1
Architecture: amd64
Date: Wed Jan 16 15:16:17 2013
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
IpRoute:
 default via 10.20.1.1 dev wlan0
 10.20.0.0/16 dev wlan0 proto kernel scope link src 10.20.206.118
MarkForUpload: True
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9:
 ** (process:9889): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files
 Error: nmcli (0.9.4.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable.
nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running.
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 not running unknown unknown unknown unknown unknown unknown unknown

[Erno Kuusela (erno-iki)]

Hmm, bug #1003842 seems to be about a schizophrenic split-dns configuration where you have a mix of internet dns and
non-internet dns servers returned from dhcp. But these errors were from browsing the web, eg youtube.com. And
I don't see evidence of this kind of dns configuration breakage anyway (name servers have neighboring ip addresses).

[Thomas Hood (jdthood)]

"This bug was fixed in the package network-manager - 0.9.6.0~git201207271115.edb85e9-0ubuntu1".