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!

If the proposal is fully agreed with the FW Merlin development team and commits not to use traffic data for commercial use, the Unbound-Asuswrt-Merlin project adds the option to NEXTDNS.
Code:
forward-zone:
  name: "."
  forward-tls-upstream: yes
  forward-addr: 45.90.28.0#XXXX.dns1.nextdns.io
  forward-addr: 2a07:a8c0::#XXXX.dns1.nextdns.io
  forward-addr: 45.90.30.0#XXXX.dns2.nextdns.io
  forward-addr: 2a07:a8c1::#XXXX.dns2.nextdns.io
 
@dave14305, I don't have that level of trust in Firefox or Mozilla. When I see collaborations at this level like this, I rather think the opposite; oh-oh! What's happening here? (Next level of fail in 3, 2, 1...).

Trusting big names to protect the little person has never been a thing, in my experience.
 
@dave14305, I don't have that level of trust in Firefox or Mozilla. When I see collaborations at this level like this, I rather think the opposite; oh-oh! What's happening here? (Next level of fail in 3, 2, 1...).

Trusting big names to protect the little person has never been a thing, in my experience.
I hear you, especially now that Mozilla is looking for more ways to monetize. But they are banking on privacy vs. Google as much as Apple is.

Just because you’re paranoid doesn’t mean they’re not out to get you. :eek::eek::eek:
 
I wonder how long this service will last before Google et al puts them out of business.
 
If the proposal is fully agreed with the FW Merlin development team and commits not to use traffic data for commercial use, the Unbound-Asuswrt-Merlin project adds the option to NEXTDNS.
Code:
forward-zone:
  name: "."
  forward-tls-upstream: yes
  forward-addr: 45.90.28.0#XXXX.dns1.nextdns.io
  forward-addr: 2a07:a8c0::#XXXX.dns1.nextdns.io
  forward-addr: 45.90.30.0#XXXX.dns2.nextdns.io
  forward-addr: 2a07:a8c1::#XXXX.dns2.nextdns.io

can i add this noow itself to unbound

i tried added my config is to this and placed it in unbound.conf file but it dosent cannot

also do i need studdy for this ??
 
can i add this noow itself to unbound

i tried added my config is to this and placed it in unbound.conf file but it dosent cannot

also do i need studdy for this ??
download.png

On post:
Post#526
 
In order not to blur the post, more information on the post:
Post#526
 
New issue after switching to John’s fork 39E3j9527 and running the latest DoH client 1.4.18.

Endpoints cannot be found on startup due to an unknown cert issue.
Code:
Jan  9 03:49:01 nextdns[8531]: Endpoint provider failed: https://router.nextdns.io?stack=dual: Get https://216.239.32.21:443?stack=dual: x509: certificate signed by unknown authority
Jan  9 03:49:02 nextdns[8531]: Endpoint failed: https://dns1.nextdns.io#45.90.28.0,2a07:a8c0::: roundtrip: x509: certificate signed by unknown authority
Jan  9 03:49:02 nextdns[8531]: Endpoint failed: https://dns2.nextdns.io#45.90.30.0,2a07:a8c1::: roundtrip: x509: certificate signed by unknown authority
This seems to be due to the non standard location of the CA bundle in John’s firmware. I was able to workaround it by linking to the bundle.
Code:
mkdir -p /tmp/etc/ssl/certs
ln -fs /rom/ca-bundle.crt /tmp/etc/ssl/certs/ca-certificates.crt
This should go into /jffs/scripts/services-start before the nextdns.init command.
 
Last edited:
New issue after switching to John’s fork 39E3j9527 and running the latest DoH client 1.4.18.

Endpoints cannot be found on startup due to an unknown cert issue.
Code:
Jan  9 03:49:01 nextdns[8531]: Endpoint provider failed: https://router.nextdns.io?stack=dual: Get https://216.239.32.21:443?stack=dual: x509: certificate signed by unknown authority
Jan  9 03:49:02 nextdns[8531]: Endpoint failed: https://dns1.nextdns.io#45.90.28.0,2a07:a8c0::: roundtrip: x509: certificate signed by unknown authority
Jan  9 03:49:02 nextdns[8531]: Endpoint failed: https://dns2.nextdns.io#45.90.30.0,2a07:a8c1::: roundtrip: x509: certificate signed by unknown authority
This seems to be due to the non standard location of the CA bundle in John’s firmware. I was able to workaround it by linking to the bundle.
Code:
mkdir -p /tmp/etc/ssl/certs
ln -fs /rom/ca-bundle.crt /tmp/etc/ssl/certs/ca-certificates.crt
This should go into /jffs/scripts/services-start before the nextdns.init command.

Thanks for the heads up, it's fixed in master: https://github.com/nextdns/nextdns/commit/6dbbfa21d0d2388f975791669e3be818fb9cfd43
 
I'm proud to announce NextDNS is now officially supporting Merlin. You can find the installation procedure on our Github Wiki.

We are also working with @RMerlin to add a UI to this integration. Stay tuned.

You can post your questions or concerns to this thread or contact us directly through our support chat on https://nextdns.io.

Enjoy and happy new year.

Now I've had more time to troubleshoot. Turned off all TrendMicro services and did a power cycle but it still doesn't work. I ran the installer with the debug:

Code:
ASUSWRT-Merlin RT-AC86U 384.14-2 Wed Jan  1 03:24:39 UTC 2020
ac86admin@RT-AC86U:/tmp/home/root# DEBUG=1 sh -c "$(curl -sL https://nextdns.io/install)"
INFO: OS: asuswrt-merlin
INFO: GOARCH: arm64
INFO: GOOS: linux
DEBUG: Start install loop with CURRENT_RELEASE=
DEBUG: NextDNS is not installed
i) Install NextDNS
e) Exit
Choice (default=i): i
INFO: Installing NextDNS...
DEBUG: Using bin install type
DEBUG: Installing 1.4.18 binary for linux/arm64 to /jffs/nextdns/nextdns
DEBUG: Start configure
DEBUG: Get configuration ID
NextDNS Configuration ID: XXXXX
DEBUG: Add arg -config=XXXXX
Report device name? [Y|n]:
DEBUG: Add arg -report-client-info=true
Enable hardened privacy mode (may increase latency)? [y|N]:
DEBUG: Add arg -hardened-privacy=false
DEBUG: Add arg -setup-router=true
Automatically configure host DNS on daemon startup? [Y|n]:
DEBUG: Add arg -auto-activate=true
NextDNS installed and started using sysv init
Error: open /etc/init.d/nextdns: read-only file system
ERROR: install: exit 0
DEBUG: Start install loop with CURRENT_RELEASE=1.4.18
DEBUG: NextDNS is up to date (1.4.18)
c) Configure NextDNS
r) Remove NextDNS
e) Exit
Choice (default=c): e
ac86admin@RT-AC86U:/tmp/home/root#


ac86admin@RT-AC86U:/jffs/nextdns# ./nextdns status
Error: "service" failed: fork/exec /sbin/service: cannot allocate memory
ac86admin@RT-AC86U:/jffs/nextdns#

I have now done a complete factory reset and will try again later when I have a chance.
 
Last edited:
I just did my first upgrade of NextDNS.

Is it expected that I still have to "install" NextDNS manually after the update?
 
Now I've had more time to troubleshoot. Turned off all TrendMicro services and did a power cycle but it still doesn't work. I ran the installer with the debug:

Code:
ASUSWRT-Merlin RT-AC86U 384.14-2 Wed Jan  1 03:24:39 UTC 2020
ac86admin@RT-AC86U:/tmp/home/root# DEBUG=1 sh -c "$(curl -sL https://nextdns.io/install)"
INFO: OS: asuswrt-merlin
INFO: GOARCH: arm64
INFO: GOOS: linux
DEBUG: Start install loop with CURRENT_RELEASE=
DEBUG: NextDNS is not installed
i) Install NextDNS
e) Exit
Choice (default=i): i
INFO: Installing NextDNS...
DEBUG: Using bin install type
DEBUG: Installing 1.4.18 binary for linux/arm64 to /jffs/nextdns/nextdns
DEBUG: Start configure
DEBUG: Get configuration ID
NextDNS Configuration ID: XXXXX
DEBUG: Add arg -config=XXXXX
Report device name? [Y|n]:
DEBUG: Add arg -report-client-info=true
Enable hardened privacy mode (may increase latency)? [y|N]:
DEBUG: Add arg -hardened-privacy=false
DEBUG: Add arg -setup-router=true
Automatically configure host DNS on daemon startup? [Y|n]:
DEBUG: Add arg -auto-activate=true
NextDNS installed and started using sysv init
Error: open /etc/init.d/nextdns: read-only file system
ERROR: install: exit 0
DEBUG: Start install loop with CURRENT_RELEASE=1.4.18
DEBUG: NextDNS is up to date (1.4.18)
c) Configure NextDNS
r) Remove NextDNS
e) Exit
Choice (default=c): e
ac86admin@RT-AC86U:/tmp/home/root#


ac86admin@RT-AC86U:/jffs/nextdns# ./nextdns status
Error: "service" failed: fork/exec /sbin/service: cannot allocate memory
ac86admin@RT-AC86U:/jffs/nextdns#

I have now done a complete factory reset and will try again later when I have a chance.

Just pushed the v1.4.19 that should fix this issue (should be available in a few minutes).
 

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!

Members online

Top