Use systemd-resolved dbus interface instead of creating *.network files on-the-fly about openvpn-update-resolv-conf

[WGH-]

However, if systemd-networkd is restarted for any reason, it'll lose all the info. The solution with temporary .network files doesn't have this problem.

[piotr-dobrogost]

I don't know systemd very well but I don't see how restarting one service (networkd) would make another service (resolved) loose any info.

[poettering]

The best option would be to push the DNS data directly into resolved, as mentioned.

Restarting networkd has no effect on resolved keeping the DNS data you pushed into it around or not. However, currently resolved will forget data you push into it if you restart resolved itself. That's certainly something we should fix though... I added that to my todo list now.

It would be fantastic if openvpn would push its discovered DNS data directly into resolved via the API we provide, and we have prepped documentation explaining how to do this:

https://wiki.freedesktop.org/www/Software/systemd/writing-network-configuration-managers/

Note that the interfaces have been added very recently only, hence you need 229 or newer to make this work.

[WGH-]

Also, it seems that implemented solution is broken on newer systemd. Restarting systemd-networkd removes the IP from the VPN interface for some reason, leaving it without one.

[WGH-]

https://github.com/jonathanio/update-systemd-resolved
This script seems to do the job. I don't really feel like rewriting what already works fine :)

[piotr-dobrogost]

Thanks for your engagement in this and the link!
Maybe update-systemd-network.sh script should be dropped then and information about https://github.com/jonathanio/update-systemd-resolved added to readme instead?

[WGH-]

The script might remain useful for distributions stuck with older systemd versions, like Debian Jessie or Gentoo stable, though. So I'm against the complete removal.

But users running newer systemd should be redirected to the better script, I think.