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

DNS lookup failure #458

Open
skwzrd opened this issue May 21, 2023 · 5 comments
Open

DNS lookup failure #458

skwzrd opened this issue May 21, 2023 · 5 comments

Comments

@skwzrd
Copy link

skwzrd commented May 21, 2023

After running the installation script, with all the default options, DNS lookups began failing.

$user> nslookup google.com
;; communications error to 127.0.0.1#53: connection refused
;; communications error to 127.0.0.1#53: connection refused
;; communications error to 127.0.0.1#53: connection refused
;; no servers could be reached

I added some namerservers to the file /etc/resolv.conf

nameserver 9.9.9.9
nameserver 208.67.222.222

And now it's working.

In the past, I had AdGuard Home installed on my server (DNS port 53), but uninstalled it before using wireguard-install.sh. I guess the script changed some configs, and made my server use 127.0.0.1:53 again?

@mcking230
Copy link

I am forced to change the file every reboot

@mator
Copy link

mator commented Jul 26, 2023

what is your operating system (name, version)? what does /etc/resolv.conf states after running the script? did you used resolvectl to setup your interfaces and dns servers?

I had the same error, seems like script uses resolvconf, but did not check if systemd-resolved is installed, so i had to install systemd-resolved (apt install systemd-resolved) and setup my public interface to use new DNS server:

$ resolvectl dns ens3 8.8.8.8

@nikit9999
Copy link

same issue here, couldn't find any reasonable solution.

@Nolux
Copy link

Nolux commented Sep 14, 2023

I have the same issue as well. Trying to revert what ever the install script has done.

@hdn012
Copy link

hdn012 commented Oct 24, 2023

It may be similar to this issue #479. In that issue, I found a solution that maybe able to help.

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

7 participants
@mator @Nolux @nikit9999 @mcking230 @skwzrd @hdn012 and others