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

Cannot resolve any DNS queries #38

Open
VPNReyMan opened this issue May 8, 2019 · 5 comments
Open

Cannot resolve any DNS queries #38

VPNReyMan opened this issue May 8, 2019 · 5 comments

Comments

@VPNReyMan
Copy link

I tested AzireVPN because they offer 3 days free when you signup (just enter in email). I setup qubes-vpn-tunnel in the template per the instructions. The VPN can connect, but it cannot resolve any DNS queries.

  1. Due to an error the vpn config file had to be modified to comment out the following:
    up /etc/openvpn/update-resolv-conf
    down /etc/openvpn/update-resolv-conf

  2. After this was done openvpn quit giving a fatal error and connected. However, despite connecting, there is no DNS. This can be tested by trying to ping google or curl google

Any suggestions on how to make this work?

@VPNReyMan
Copy link
Author

Tried with mullvad and their script comes with an update-resolv-conf. It appears these scripts are only tested with Debian / Fedora 28. I am using Fedora 29 and there appears to be serious issues with any DNS resolving. It might be useful to put in the docs that this only works with debian and fedora 28, so people do not waste time trying it on fedora 29+

@tasket
Copy link
Owner

tasket commented May 9, 2019

Thanks for the report! I'll definitely look into this.

BTW, the up/down script error probably shouldn't happen at all; qubes-vpn-setup will filter out certain commands from an openvpn conf before startup. The filtered version goes in the /tmp directory and the original is unaltered.

@tasket
Copy link
Owner

tasket commented Jun 18, 2019

@VPNReyMan I just did a ProxyVM install of the 1.4.1 branch with Fedora 30 using an Azire free account (using the Sweden server) ...and it works! The log says "Using DNS servers 91.231.153.2" and when I check dnat with 'iptables -L -v -t nat' that DNS address is in PR-QBS.

Let me know if this is still a problem for you. (Also see my update of issue #39.)

@tortugaverde98
Copy link

Problems with name resolution after script v1.4.2 is installed, on debian 10 minimal.
Before running the script, as recommended on the readme page, I test connectivity:
sudo openvpn --cd /rw/config/vpn --config vpn-client.conf --auth-user-pass userpassword.txt
The test is successful. I even attach a temp VM to it , run firefox, and a website tells me I'm exiting out of the desired country. After installing the script in the proxyVM like so:
sudo bash ./install

without error, then rebooting, nothing happens. I again run the test command as above and it returns:
RESOLVE: Cannot resolve host address: servername:port (Temporary failure in name resolution)

In an attempt to remedy, I installed resolvconf in the template and tried again, with the same result. nslookup is not installed. Is it a requirement? I'm very hesistant to attempt modifying other variables or config files as it seems the problem is introduced with the qubes-vpn-support script.

@tortugaverde98
Copy link

I tried qubes-tunnel with a different template and a different temp VM and in the end had the same result. OpenVPN connected when told to test it, but after setting qubes-tunnel-openvpn and running sudo /usr/lib/qubes/qtunnel-setup --config, then rebooting, name resolution no longer works. I also don't get any notifications whatsoever at any point during startup, but that doesn't seem like a root cause, but a problem to be solved later.

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

3 participants