DNS name resolving does not work with VPNC connection

Bug #1589816 reported by LGB [Gábor Lénárt] on 2016-06-07
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
vpnc (Ubuntu)
Undecided
Unassigned

Bug Description

I've configured (with network manager) a VPNC connection, address only, ie "split tunnel" mode. However, after connecting, though everything works, I am unable to resolve "internal" domains having "pseudo" TLD as .intra in names. Note, that I set up a single DNS server for the VPN connection, and indeed that DNS server after VPN connections answers (tested with "host something.intra. 172.21.0.1" command, the same 172.21.0.1 is given for the VPN configuration), just there should be a bug here in vpnc/ubuntu that name server is not asked for the given name, I guess ...

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: vpnc 0.5.3r550-2build1
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jun 7 08:28:58 2016
InstallationDate: Installed on 2015-07-10 (332 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
SourcePackage: vpnc
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.vpnc.default.conf: [deleted]

LGB [Gábor Lénárt] (lgb) wrote :
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers