You are not logged in.
Pages: 1
Topic closed
After I read this statement
However if you have systemd 229 or newer the better option is to use script from https://github.com/jonathanio/update-systemd-resolved which uses DBus calls instead of creating temporary *.network files.
here
I tried to prevent DNS leaking with the update-systemd-resolved script, but I don't get it to work.
My DNS is always leaking.
I installed updated-systemd-resolved via AUR, the
systemd-resolved.service
is enabled
and I modified my
/etc/nsswitch.conf
with this line
# Don't use /etc/resolv.conf at all
hosts: files resolve myhostname
and added following lines to my openvpn client file
script-security 2
setenv PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
up /etc/openvpn/update-systemd-resolved
down /etc/openvpn/update-systemd-resolved
down-pre
When I check the status of systemd-resolved.service after I started openvpn
I see
systemd-resolved[535]: Switching to DNS server XXX.XXX.XX.X for interface tun0.
with XXX is the IP pushed from the openvpn server.
But when I do a DNS Leaktest, my DNS is always leaking!
Some help would be really appreciated!
Last edited by john-soda (2017-05-30 09:58:15)
Offline
When I add this line in my openvpn client config
dhcp-option DOMAIN-ROUTE .
it works!
See: Github issue
Offline
Cool. Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.
Offline
When I add this line in my openvpn client config
dhcp-option DOMAIN-ROUTE .
it works!
See: Github issue
Thanks a lot for posting the solution! It works
Offline
@dmitryb
Please take the time to familiarise yourself with the forum Code of Conduct, especially the sections regarding necro-bumping and empty posts.
Closing this old thread.
Offline
Pages: 1
Topic closed