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 entries are sticking after disconnecting from NordVPN #26

Open
dbolger opened this issue May 21, 2023 · 3 comments
Open

DNS entries are sticking after disconnecting from NordVPN #26

dbolger opened this issue May 21, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@dbolger
Copy link

dbolger commented May 21, 2023

I have a static nameserver defined in /etc/dhcpcd.conf that is being overwritten and not being returned to /etc/resolv.conf after disconnecting from NordVPN.

Before connecting to NordVPN:

# Generated by resolvconf
nameserver 192.168.50.13

After connecting to NordVPN:

# Generated by NordVPN
nameserver 103.86.96.100
nameserver 103.86.99.100

After disconnecting from NordVPN:

# Generated by resolvconf
nameserver 103.86.96.100
nameserver 103.86.99.100
@dbolger
Copy link
Author

dbolger commented May 21, 2023

Ah, I just noticed that Arch Linux isn't on the list of supported distros.

Is Arch support coming in the future?

Edit: #3, I'm blind

@EmilijusS EmilijusS added the bug Something isn't working label May 23, 2023
@EmilijusS
Copy link
Contributor

Hello and thank you for reporting an issue. I couldn't reproduce it on Ubuntu and unfortunately we do not officially support Arch, so we aren't going to investigate this issue further at this time.

On the other hand we gladly accept community contributions and if a Pull Request with the fix would be created we could merge it.

@saucecode
Copy link

Since this is appears as a top search result, I now share how I fixed this on my arch machine.

After disconnecting with nordvpn d and DNS requests stopped working.

/etc/resolv.conf still showed the NordVPN name servers. The command resolvectl also confirms that those nameservers are still loaded.

I manually edited /etc/resolvconf adding 1.1.1.1 and 8.8.8.8, then ran sudo systemctl restart systemd-resolved

Confirmed that the changes are reflected when running resolvectl.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants