Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for resolvconf interface #252

Open
basos9 opened this issue Apr 15, 2024 · 1 comment
Open

Add support for resolvconf interface #252

basos9 opened this issue Apr 15, 2024 · 1 comment

Comments

@basos9
Copy link

basos9 commented Apr 15, 2024

For systems with more complex DNS configurations, that also do not want to use systemd-resolved, it would be convenient to add support for resolvconf interface, in the same way as NetworkManager also supports this.

@dsommers
Copy link
Member

Do you have any pointers to how NetworkManager integrates with resolvconf?

The challenge with /etc/resolv.conf based DNS resolver configuration is that it does not support split-DNS. So I don't quite fully understand how that fits into "more complex DNS configurations". Using only /etc/resolv.conf will always send DNS queries to the first responding nameserver line.

I've been pondering on adding support for dnsmasq support, though, which can also be used by NetworkManager as well. There might still need to be a few "running methods", depending on if NetworkManager is to be involved or not.

Otherwise, to use a similar approach to resolvconf interacting directly with /etc/resolv.conf, OpenVPN 3 Linux can use that as well instead of systemd-resolved:

  # openvpn3-admin netcfg-service --config-unset systemd-resolved
  # openvpn3-admin netcfg-service --config-set resolv-conf /etc/resolv.conf

Then you need to ensure the openvpn3-service-netcfg service is stopped and restarted. This will require all VPN sessions to be stopped first; this process is responsible for providing the tun/dco interfaces to the VPN client processes (openvpn3-service-client).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants