https://www.puppeteers.net/tags/systemd-resolved/ Recent content in Systemd-Resolved on Puppeteers Oy Hugo en-US Tue, 03 Nov 2020 00:00:00 +0000 https://www.puppeteers.net/blog/making-per-link-dns-servers-pushed-from-openvpn-to-systemd-resolved-survive-networkmanager-connection-changes/ Tue, 03 Nov 2020 00:00:00 +0000 https://www.puppeteers.net/blog/making-per-link-dns-servers-pushed-from-openvpn-to-systemd-resolved-survive-networkmanager-connection-changes/ <p><strong>Update:</strong> the problem described in this article seems to be resolved in Fedora 36 (NetworkManager 1.38.0-2.fc36). It is still present in Fedora 35 (NetworkManager 1.32.12-2.fc35).</p> <p><strong>Update:</strong> there a companion article about solving this problem for Wireguard in <a href="https://www.puppeteers.net/blog/making-per-link-dns-servers-added-by-wireguard-to-systemd-resolved-survive-networkmanager-connection-changes/">here</a>.</p> <p>In an the <a href="https://www.puppeteers.net/blog/manage-linux-client-dns-settings-in-openvpn-and-wireguard/">Manage Linux client DNS settings in OpenVPN and Wireguard</a> article we described how to use the <a href="https://github.com/jonathanio/update-systemd-resolved">update-systemd-resolved</a> script to update systemd-resolved per-link DNS servers automatically based on DNS servers pushed from an OpenVPN server. This is very convenient if you have to be connected to multiple remote locations each with their own DNS servers and zones.</p>