What's new

NextDNS Installer

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Just pushed the v1.4.19 that should fix this issue (should be available in a few minutes).
Despite the addition of the TZ variable to the init script, the syslog timestamps are still in UTC. Currently 21:12 where I am. Showing 02:00. Not urgent, but there must be something deeper that determines it.
Code:
Jan 10 02:09:10 nextdns[28031]: Recieved signal: terminated
Jan 10 02:09:10 nextdns[28031]: Stopping NextDNS 1.4.19/linux
Jan 10 02:09:10 nextdns[28031]: Restore router settings
Jan 10 02:09:10 nextdns[28031]: Restore router settings: open /tmp/resolv.dnsmasq: no such file or directory
Jan 10 02:09:10 nextdns[28031]: NextDNS 1.4.19/linux stopped
Jan  9 21:09:11 nextdns.init: Stopped
Jan 10 02:09:11 nextdns[28113]: Starting NextDNS 1.4.19/linux on 127.0.0.1:5342
Jan 10 02:09:11 nextdns[28113]: Listening on TCP/127.0.0.1:5342
Jan 10 02:09:11 nextdns[28113]: Listening on UDP/127.0.0.1:5342
Jan 10 02:09:11 nextdns[28113]: Starting discovery resolver
 
No, it should reinstall itself with the same configuration. Didn't work for you?
Indeed. Same after upgrading from 1.4.18 to 1.4.19, but maybe I'm doing it wrong?

Code:
admin@ac86u:/tmp# /jffs/nextdns/nextdns version
nextdns version 1.4.18

admin@ac86u:/tmp# sh -c "$(curl -sL https://nextdns.io/install)"
INFO: OS: asuswrt-merlin
INFO: GOARCH: armv7
INFO: GOOS: linux
u) Upgrade NextDNS from 1.4.18 to 1.4.19
c) Configure NextDNS
r) Remove NextDNS
e) Exit
Choice (default=u): u
INFO: Upgrading NextDNS...
c) Configure NextDNS
r) Remove NextDNS
e) Exit
Choice (default=c): e

admin@ac86u:/tmp# /jffs/nextdns/nextdns status
not installed
 
Indeed. Same after upgrading from 1.4.18 to 1.4.19, but maybe I'm doing it wrong?

Code:
admin@ac86u:/tmp# /jffs/nextdns/nextdns version
nextdns version 1.4.18

admin@ac86u:/tmp# sh -c "$(curl -sL https://nextdns.io/install)"
INFO: OS: asuswrt-merlin
INFO: GOARCH: armv7
INFO: GOOS: linux
u) Upgrade NextDNS from 1.4.18 to 1.4.19
c) Configure NextDNS
r) Remove NextDNS
e) Exit
Choice (default=u): u
INFO: Upgrading NextDNS...
c) Configure NextDNS
r) Remove NextDNS
e) Exit
Choice (default=c): e

admin@ac86u:/tmp# /jffs/nextdns/nextdns status
not installed

You are right. It is now fixed.
 
Just pushed the v1.4.19 that should fix this issue (should be available in a few minutes).

Some error message about activating, appears to work though.

Code:
ac86admin@RT-AC86U:/jffs/nextdns# ./nextdns log
Jan 10 11:03:34 nextdns[2894]: Starting NextDNS 1.4.19/linux on 127.0.0.1:5342
Jan 10 11:03:34 nextdns[2894]: Listening on TCP/127.0.0.1:5342
Jan 10 11:03:34 nextdns[2894]: Starting discovery resolver
Jan 10 11:03:34 nextdns[2894]: Listening on UDP/127.0.0.1:5342
Jan 10 11:03:34 nextdns[2894]: Discovered(mdns) 192.168.100.200 = DISKSTATION
Jan 10 11:03:39 nextdns[2894]: Setting up router
Jan 10 11:03:39 nextdns[2894]: Activating
Jan 10 11:03:39 nextdns[2894]: Activate: activate: 127.0.0.1:5342: non 53 port not supported
Jan 10 11:03:39 nextdns[2894]: Recieved signal: child exited (ignored)
Jan 10 11:03:55 nextdns[2894]: Recieved signal: hangup (ignored)
Jan 10 11:03:58 nextdns[2894]: Connected 45.90.28.0:443 (con=20ms tls=171ms, TLS13)
Jan 10 11:03:58 nextdns[2894]: Connected 185.94.188.30:443 (con=20ms tls=44ms, TLS13)
Jan 10 11:03:58 nextdns[2894]: Switching endpoint: https://m247-ams-1.edge.nextdns.io#185.94.188.30,2001:ac8:22::100
 
@Olivier Poitrey More feedback specific to John's fork (uname -o="ASUSWRT-Merlin-LTS"):
  • During setup, it does not find /tmp/resolv.dnsmasq because it is not used on this firmware. In dnsmasq it uses "resolv-file=/tmp/resolv.conf" which contains "nameserver 1.1.1.1" entries instead of "server=" entries.
  • Check nvram stubby_proxy=1 or 0 instead of dnspriv_enabled=1 or 0 in Merlin.
Perhaps because of the setup error it is not restarting dnsmasq on install or stopping and not removing /jffs/configs/dnsmasq.conf.add. So I usually end up restarting dnsmasq manually.
Code:
Jan 10 16:00:31 nextdns[5454]: Setting up router
Jan 10 16:00:31 nextdns[5454]: Setting up router: open /tmp/resolv.dnsmasq: no such file or directory
Jan 10 16:00:31 nextdns[5454]: Recieved signal: child exited (ignored)
Jan 10 16:15:52 nextdns[5454]: Recieved signal: terminated
Jan 10 16:15:52 nextdns[5454]: Stopping NextDNS 1.4.19/linux
Jan 10 16:15:52 nextdns[5454]: Restore router settings
Jan 10 16:15:52 nextdns[5454]: Restore router settings: open /tmp/resolv.dnsmasq: no such file or directory
Jan 10 16:15:52 nextdns[5454]: NextDNS 1.4.19/linux stopped
Jan 10 11:15:54 nextdns.init: Stopped
The majority of users on this forum are using Merlin's current firmware, so you may not want to invest too heavily in adaptations for John's fork.
 
@Olivier Poitrey More feedback specific to John's fork (uname -o="ASUSWRT-Merlin-LTS"):
  • During setup, it does not find /tmp/resolv.dnsmasq because it is not used on this firmware. In dnsmasq it uses "resolv-file=/tmp/resolv.conf" which contains "nameserver 1.1.1.1" entries instead of "server=" entries.
  • Check nvram stubby_proxy=1 or 0 instead of dnspriv_enabled=1 or 0 in Merlin.
Perhaps because of the setup error it is not restarting dnsmasq on install or stopping and not removing /jffs/configs/dnsmasq.conf.add. So I usually end up restarting dnsmasq manually.
Code:
Jan 10 16:00:31 nextdns[5454]: Setting up router
Jan 10 16:00:31 nextdns[5454]: Setting up router: open /tmp/resolv.dnsmasq: no such file or directory
Jan 10 16:00:31 nextdns[5454]: Recieved signal: child exited (ignored)
Jan 10 16:15:52 nextdns[5454]: Recieved signal: terminated
Jan 10 16:15:52 nextdns[5454]: Stopping NextDNS 1.4.19/linux
Jan 10 16:15:52 nextdns[5454]: Restore router settings
Jan 10 16:15:52 nextdns[5454]: Restore router settings: open /tmp/resolv.dnsmasq: no such file or directory
Jan 10 16:15:52 nextdns[5454]: NextDNS 1.4.19/linux stopped
Jan 10 11:15:54 nextdns.init: Stopped
The majority of users on this forum are using Merlin's current firmware, so you may not want to invest too heavily in adaptations for John's fork.

Could you please open a ticket on github about this? It would be easier to follow.
It's not a huge effort to support it, no worries.
 
Despite the addition of the TZ variable to the init script, the syslog timestamps are still in UTC. Currently 21:12 where I am. Showing 02:00. Not urgent, but there must be something deeper that determines it.
Code:
Jan 10 02:09:10 nextdns[28031]: Recieved signal: terminated
Jan 10 02:09:10 nextdns[28031]: Stopping NextDNS 1.4.19/linux
Jan 10 02:09:10 nextdns[28031]: Restore router settings
Jan 10 02:09:10 nextdns[28031]: Restore router settings: open /tmp/resolv.dnsmasq: no such file or directory
Jan 10 02:09:10 nextdns[28031]: NextDNS 1.4.19/linux stopped
Jan  9 21:09:11 nextdns.init: Stopped
Jan 10 02:09:11 nextdns[28113]: Starting NextDNS 1.4.19/linux on 127.0.0.1:5342
Jan 10 02:09:11 nextdns[28113]: Listening on TCP/127.0.0.1:5342
Jan 10 02:09:11 nextdns[28113]: Listening on UDP/127.0.0.1:5342
Jan 10 02:09:11 nextdns[28113]: Starting discovery resolver

Fixed in https://github.com/nextdns/nextdns/commit/6983c9c3a2ea0c45be108e215204527d58b59cfa.
 
NextDNS via DoH was more stable for a week (than DoT), but now I again have no DNS...

Already restarted router and nextdns executable. What else can I try? (before disabling NextDNS)
 
Temporarily configured 1.1.1.1 as DNS (without encryption) and updated to 1.4.20 (then removed 1.1.1.1 again).

DNS is working again (but for how long this time?).
 
Last edited:
Still not working right, even though the file is downloaded and linked to /etc/localtime. Still getting UTC times.

EDIT: putting “unset TZ” in the nextdns.init script fixes the timezone issue for me. Go won’t look at localtime if TZ is set.

The other fixes for John’s fork work great! Thanks!


Which tz do you have in your settings?
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top