*** This bug is a duplicate of bug 1003842 ***
https://bugs.launchpad.net/bugs/1003842
Thomas:
After doing some more research I found what was causing the VPN DNS resolution
in my specific scenario. Based on some comments in bug #959037, I found that
the bind9 service was installed and running. After uninstalling bind9 using
synaptic and restarting the networkmanager service, name to IP resolution began
working. Also the file /var/run/nm-dns-dnsmasq.conf showed up and was being
correctly populated.
Here's what my config files look like now with VPN connection (edited to
protect company security). Based on your prior response, I'm confused
as to why resolv.conf has more than just the loopback IP. It works,
though.
/etc/resolv.conf:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver {first vpn dns IP addr in network manager}
nameserver {second vpn dns IP addr in network manager}
nameserver 127.0.0.1
search {first vpn search domain in network manager} {second vpn search domain
in network manager}
/var/run/nm-dns-dnsmasq.conf:
server={first vpn dns IP addr in network manager}
server={second vpn dns IP addr in network manager}
--
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/994575
Title:
dnsmasq does not update nameserver info after network change
Status in “network-manager” package in Ubuntu:
Confirmed
Bug description:
I have a VPN set up in Network Manager, which worked well when my
system was running 11.10.
After upgrading to 12.04, I've noticed that DNS changes needed by the
VPN aren't happening. Hosts that only resolve within the VPN won't
resolve, and hosts that are supposed to resolve with different IP
addresses inside the VPN don't.
I can see the new, proper nameserver configuration in /var/run/nm-dns-
dnsmasq.conf. I can resolve properly if I query the name server
directly, i.e. "host <name-to-resolve> <vpn-dns-server-ip>". And, if
I use that IP address instead of the name, I can successfully do
things like ssh. But simple resolution appears to still be using the
old name server.
At one point, I killed off dnsmasq and wrote a new /etc/resolv.conf
with the VPN name servers. That worked, but caused all manner of
problems later.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.4.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Fri May 4 09:04:23 2012
EcryptfsInUse: Yes
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
IpRoute:
default via 192.168.50.2 dev eth0 proto static
169.254.0.0/16 dev eth0 scope link metric 1000
192.168.50.0/24 dev eth0 proto kernel scope link src 192.168.50.222
metric 1
192.168.50.0/24 dev wlan0 proto kernel scope link src 192.168.50.106
metric 2
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: Upgraded to precise on 2012-05-02 (1 days ago)
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
eth0 802-3-ethernet connected
/org/freedesktop/NetworkManager/Devices/1
wlan0 802-11-wireless connected
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE
WIFI WWAN-HARDWARE WWAN
running 0.9.4.0 connected enabled enabled
enabled enabled disabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/994575/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
