Split-DNS not working in vpnc-scripts after renaming systemd-resolve to resolvectrl
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
vpnc-scripts (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Setting up a VPN with openconnect and split DNS is not working correctly after dist-upgrade from 21.10 to 22.04. The vpnc-script still refers to "systemd-resolve" to check for systemd-resolved and fails due to the name change to "resolvectl". Thus the DNS servers are written into the resolve.conf and thus breaks the split DNS functionality.
As a quick workaround it was sufficient to create a symlink:
sudo ln /usr/bin/resolvectl /usr/bin/
As fix I would suggest to update the vpnc-script to use "resolvectl".
Source: /usr/share/
grep '^hosts' /etc/nsswitch.conf 2>/dev/null|grep resolve >/dev/null 2>&1 && command systemd-resolve --status >/dev/null 2>&1
if [ $? = 0 ];then
RESOLVEDENABLED=1
else
RESOLVEDENABLED=0
fi
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity (not installed)
ProcVersionSign
Uname: Linux 5.15.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: KDE
Date: Mon Sep 19 14:35:43 2022
InstallCmdLine: BOOT_IMAGE=
InstallationDate: Installed on 2019-01-12 (1345 days ago)
InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2)
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
Symptom: installation
UpgradeStatus: Upgraded to jammy on 2021-12-03 (290 days ago)
Hello Michael,
thank you for reporting the issue. According to your description the problem is with package vpnc-scripts and not ubiquity.
Could you, please, describe how to set up and test a split DNS scenario.
Best regards
Heinrich