Opened 7 years ago
Last modified 3 years ago
#753 assigned Bug / Defect
OpenVPN should update systemd-resolved on systems running it
Reported by: | flavor8 | Owned by: | David Sommerseth |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | Generic / unclassified | Version: | OpenVPN git master branch (Community Ed) |
Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | |
Cc: | piotr.dobrogost |
Description
systemd-resolved is used by many programs (e.g. ssh, ping, psql) to do DNS lookups, and maintains a DNS cache. After starting openvpn on a system with systemd-resolved, this cache is not automatically flushed / updated, and therefore resources provided by the VPN are not accessible by name.
There is a community supplied script that allows openvpn to update systemd directly. Please evaluate it and add post-initialization logic to openvpn to force systemd-resolved to update/flush its cache.
Change History (6)
comment:1 Changed 7 years ago by
Owner: | set to David Sommerseth |
---|---|
Status: | new → assigned |
Version: | 2.2.2 → git master branch |
comment:3 Changed 7 years ago by
Cc: | piotr.dobrogost added |
---|
comment:5 follow-up: 6 Changed 3 years ago by
Wow. Five year old open bug - it'll be starting first grade soon!
comment:6 Changed 3 years ago by
Replying to nobodyusesusernamesanymore:
Wow. Five year old open bug - it'll be starting first grade soon!
If it is urgent for you, use OpenVPN 3 Linux. It ships with systemd-resolved support. And with the coming v14_beta release, it will be enabled by default on Fedora and Ubuntu 20.04 and newer.
If that's not acceptable and you need a quicker response, patches are welcome. Sarcastic comments does not change the priority.
... since you're working on better systemd integration anyway...