<div dir="ltr"><div dir="ltr">On Mon, Sep 16, 2019 at 2:14 PM Marc Haber <<a href="mailto:mh%2Bsystemd-devel@zugschlus.de">mh+systemd-devel@zugschlus.de</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
when I run an OpenVPN interface, OpenVPN manages the interface itself:<br>
It handles creation, destruction and assignment of the IP address. The<br>
IP address can be controlled by the remote site, so the OpenVPN daemon<br>
is kind of the only thing that can configured the Interface.<br>
<br>
I would, however, like systemd-resolved to ask DNS servers that are<br>
reachable over the VPN for certain domains, such as <a href="http://ka51.zugschlus.de" rel="noreferrer" target="_blank">ka51.zugschlus.de</a>.<br>
<br>[...]<br>
<br>
Can I have the advantages of systemd-resolved on an Interface that is<br>
not fully managed by systemd-networkd?<br></blockquote><div><br></div><div>There are post-up scripts for OpenVPN which can load DNS configuration into systemd-resolved:</div><div><br></div><div><a href="https://github.com/jonathanio/update-systemd-resolved">https://github.com/jonathanio/update-systemd-resolved</a><br></div><div><a href="https://packages.debian.org/sid/openvpn-systemd-resolved">https://packages.debian.org/sid/openvpn-systemd-resolved</a><br></div><div><br></div></div><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">Mantas Mikulėnas</div></div></div>