Giter Club home page Giter Club logo

Comments (8)

rs avatar rs commented on May 22, 2024 1

The main problem was the restart of NetworkManager instead of reload, which was disturbing the boot process. Other commits are to fix errors you always get at startup because the network is not yet reachable. Your log output should be cleaner now.

from nextdns.

rs avatar rs commented on May 22, 2024

What do you get for nextdns version and nextdns config.

from nextdns.

mendhak avatar mendhak commented on May 22, 2024

Oh I'm sorry I didn't include the config earlier.

nextdns version

nextdns version 1.3.0

nextdns config

listen localhost:53
config xxxxxx
log-queries false
report-client-info true
detect-captive-portals false
hardened-privacy false
bogus-priv true
timeout 5s
auto-activate false

I also tried an apt purge nextdns and then reinstall it and then re-set it up with

sudo nextdns install -report-client-info -config xxxxxx -auto-activate

(So auto-activate becomes true in the above config) - but that made no difference either. After a reboot, the conf file is still being overwritten. As before, the systemctl status for nextdns looks the same as first post.

from nextdns.

mendhak avatar mendhak commented on May 22, 2024

I also see

$ cat /etc/NetworkManager/conf.d/nextdns.conf 
[main]
dns=none

So that should prevent anything overwriting /etc/resolv.conf is that right? (I am not knowledgeable in this area)

from nextdns.

rs avatar rs commented on May 22, 2024

Can you send your journalctl -b just after a full boot?

from nextdns.

mendhak avatar mendhak commented on May 22, 2024

OK here you go, thanks for looking at it

issue33-journalctlb.txt

from nextdns.

rs avatar rs commented on May 22, 2024

Please try 1.3.1

from nextdns.

mendhak avatar mendhak commented on May 22, 2024

You've done it! I've rebooted multiple times now and nextdns is sticking in place. Thanks for your help with both issues.

So if I'm understanding it right, you had to do a reload instead of try-restart, and also set the dependency on network.target instead of network-online.target - I see some more commits after that but I guess that is to help with future troubleshooting and maintenance.

In the meantime I had been using a workaround - I added dns=none under [main] in the /etc/NetworkManager/Networkmanager.conf file to get nextdns settings to persist.

from nextdns.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.