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 servers randomly alternating between NextDNS and my ISP's (Debian) #307

Closed
paps opened this issue Aug 25, 2020 · 7 comments
Closed

DNS servers randomly alternating between NextDNS and my ISP's (Debian) #307

paps opened this issue Aug 25, 2020 · 7 comments
Labels
🐞 bug Something isn't working

Comments

@paps
Copy link

paps commented Aug 25, 2020

Hi, thanks a lot for this great project.

I have a very simple setup on Debian Sid, nothing much installed, not even NetworkManager.

I've installed nextdns by doing the recommended sh -c "$(curl -sL https://nextdns.io/install)"

And here's what I get when I look at my dashboard, an alternating resolver (I'm not even refreshing the page):
Peek 2020-08-26 00-20

"Orange" is my ISP. I'm behind their provider router (ethernet) which obviously advertises their own DNS servers through DHCP (if that matters)

When I run sudo systemctl restart nextdns I see

Aug 26 00:28:11 paris nextdns[430529]: Activating
Aug 26 00:28:11 paris nextdns[430529]: Activate: NetworkManager resolver management: exit status 1

in the systemd logs which does not look too good, but then things start resolving (be it on orange or nextdns)

Any idea about what might cause this? Thanks

Context

  • Version 1.7.1
  • Platform Debian Sid/unstable
@paps paps added the 🐞 bug Something isn't working label Aug 25, 2020
@theeddie
Copy link

Just want to point out I have the same issue

@whitedragon551
Copy link

Also have the same issue, running this on the UDMP.

@paps
Copy link
Author

paps commented Dec 28, 2020

So like I said in my original post, I didn't even have the NetworkManager running.

Turns out that

  • installing network-manager (and network-manager-gnome but I guess this one is not needed)
  • and changing managed=false to managed=true in /etc/NetworkManager/NetworkManager.conf
  • and enabling and starting the NetworkManager service with:
    • sudo systemctl enable NetworkManager
    • sudo systemctl start NetworkManager

fixed my problem.

Seems like there are strong interactions between NetworkManager and NextDNS, I'm not sure exactly why or how. Anyway, that fixed it for me and I don't see anything wrong in having NetworkManager running on both desktop PCs I run

@paps
Copy link
Author

paps commented Jan 8, 2021

Nevermind, I spoke too fast.

What I said above ☝️ is incorrect, it does not fix the problem

Anybody have a clue?

@rs
Copy link
Contributor

rs commented Jan 8, 2021

Can you please try to disable auto activate sudo nextdns config set -auto-activate=false; sudo nextdns restart then set manually your DNS to 127.0.0.1 in /etc/resolv.conf to see if it resolves the issue?

@rs
Copy link
Contributor

rs commented Jan 8, 2021

If it still does not work, you might be using a non supported DHCP client that overrides /etc/resolv.conf. Make sure you disable that.

@paps
Copy link
Author

paps commented May 22, 2021

Alright thanks, I finally figured it out. Adding (or rather, uncommenting) the prepend domain-name-servers 127.0.0.1; line in /etc/dhcp/dhclient.conf solves the problem

This makes me believe that NextDNS does not work by default on Debian sid. Dhclient regularly overrides resolv.conf with parameters coming from the network.

you might be using a non supported DHCP client

I mean... I'm using all the defaults from Debian sid, I haven't touched anything. What do you think?

@paps paps closed this as completed May 22, 2021
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

4 participants