NextDNS Installer

[thewan]

When using this installer, is there anyway to set certain devices to not use NextDNS and just use the router's DNS? There are devices that don't play well with NextDNS relatively high latency since its not consistent in picking your closest node. I would like those devices to just use other DNS instead.

 

[Olivier Poitrey]

When using this installer, is there anyway to set certain devices to not use NextDNS and just use the router's DNS? There are devices that don't play well with NextDNS relatively high latency since its not consistent in picking your closest node. I would like those devices to just use other DNS instead.

It should always pick the closest one. Contact us on support chat if it does not.

 

[SomeWhereOverTheRainBow]

When using this installer, is there anyway to set certain devices to not use NextDNS and just use the router's DNS? There are devices that don't play well with NextDNS relatively high latency since its not consistent in picking your closest node. I would like those devices to just use other DNS instead.

Dns filter on the router. But it is in the routers gui and not the installer.

 

[thewan]

It should always pick the closest one. Contact us on support chat if it does not.

I have contacted support chat before. The issue improved for a while, but right now it became worse and seems to have connected to an even further node than usual, based on the ping page.

I am just trying to to see if I can set some devices to just use other DNS. Most of the users in the house don't mind the random latency jumps, but for others that do mind, or for those IOT devices that seem to respond poorly, I would like to just use other DNS in the meantime while wating for it to be fixed. It's faster to just do so instead of troubleshooting with support which I understand will take time.

Dns filter on the router. But it is in the routers gui and not the installer.

This doesn't seem to work if the installer is used. I tried using dnsfilter to other DNS, cloudflare for example, but those devices still end up using nextdns based on the logs. One of the reasons I prefer to use the installer is that it at least sometimes connect to my nearest node. Using dot in merlin, or using Android's private DNS features seems to permanently connect to further nodes.

 

[Olivier Poitrey]

The cli will use geo steering to send you to the closest pop. I would be curious to understand how it does not work for you.

There is no easy way to do what you ask for with cli. Please contact us on the chat again so we can understand your issue.

 

[Zastoff]

I have contacted support chat before. The issue improved for a while, but right now it became worse and seems to have connected to an even further node than usual, based on the ping page.

I am just trying to to see if I can set some devices to just use other DNS. Most of the users in the house don't mind the random latency jumps, but for others that do mind, or for those IOT devices that seem to respond poorly, I would like to just use other DNS in the meantime while wating for it to be fixed. It's faster to just do so instead of troubleshooting with support which I understand will take time.



This doesn't seem to work if the installer is used. I tried using dnsfilter to other DNS, cloudflare for example, but those devices still end up using nextdns based on the logs. One of the reasons I prefer to use the installer is that it at least sometimes connect to my nearest node. Using dot in merlin, or using Android's private DNS features seems to permanently connect to further nodes.

Would recommend to test with DNSCrypt installer instead and set it up with NextDNS, DNS-filter will work fine with that installer.

 

[Mr Tvardovsky]

Hello, a long-time-reader-but-first-time-writer here. Have mercy and patience on me, guys

I have got the NextDNS cli client installed on my RT-AC66u_B1, running Merlin 384.19. I am on a paid yearly subscription and overall I am happy with the service. There is though one detail which doesn't work for me as good as it promises which is logging the devices by their names. The IoT devices (like e.g. MusicCast speakers) are the biggest mess, but even my iPhone sometimes logs under its original iOS name, sometimes it shows up as an asterisk and sometimes under the device ID from the https://test.nextdns.io/ webpage. The only thing that is consistent is the IP address of each device.

It doesn't fundamentally affect the overall NextDNS functionality, but it would be nice to get it right and e.g. be able to immediately and reliably differentiate the online activity of my daughter and my son on their respective devices Would you have any idea what may be causing it? Or even better, how to fix it?

 

[XIII]

Did not know about that test page...

Thanks for sharing!

 

[alekos]

How can I ensure my router enforces DNSSEC, DoT and DoH when using NextDNS?
I recently changed my settings to whats posted in the image. I am just using amtm/nextdns script.

 

[dave14305]

How can I ensure my router enforces DNSSEC, DoT and DoH when using NextDNS?
I recently changed my settings to whats posted in the image. I am just using amtm/nextdns script.

View attachment 25752

The nextdns CLI will disable DNSSEC and DNS Rebind because it interferes with the adblocking.

 

[XIII]

@Olivier Poitrey I noticed that this test page performs a GET request to a secured version with a unique(?) ID in front of the URL.

If I want to immediately perform that GET request, which URL should I use? (only the one with the ID in front seems to work? And how do I know which ID?)

 

[Mr Tvardovsky]

Dear @Olivier Poitrey , when you respond, could you also kindly look at my question from the post #507 above?

 

[alekos]

I have a freshly reset RT-AC86U [384.19] and have installed nextdns from the github page. Installation goes smoothly, but upon a restart of the router, when I run the 'nextdns' command, it says:
-sh: nextdns: not found
I don't have anything else installed at this point, just a stock setup with dns servers added for nextnds on ipv4 (ipv6 disabled). When I check 'services-start' it looks fine with:
[#!/bin/sh
/jffs/nextdns/nextdns.init start]
and [/jffs/nextdns] has the 3 files all visible. When I run the installer again, it remembers my id when I go through the config. Also, when I run ps -w, it shows:
[1404 malaka 782m S /jffs/nextdns/nextdns run]
so does it mean its running but I just can't access any of the nextdns commands?

 

[XIII]

Do you also have this link?

/opt/sbin/nextdns -> /jffs/nextdns/nextdns

 

[iJorgen]

I have a freshly reset RT-AC86U [384.19] and have installed nextdns from the github page. Installation goes smoothly, but upon a restart of the router, when I run the 'nextdns' command, it says:
-sh: nextdns: not found

Similar experience here. After a reboot I must always enter the full path /jffs/nextdns/nextdns <command>. Should it work to just enter "nextdns"?

 

[alekos]

I started getting errors (fatal runtime out of memory) errors a week or so ago. I have a 3 year old RT-AC86U with a fresh flash of latest asuswrt-merlin. I just tried running an upgrade for NextDNS and received these errors below. Could this be my memory failing on the router?

ASUSWRT-Merlin RT-AC86U 384.19_0 Fri Aug 14 19:19:51 UTC 2020
malaka@WRTMERLIN:/tmp/home/root# sh -c "$(curl -sL https://nextdns.io/install)"
INFO: OS: asuswrt-merlin
INFO: GOARCH: armv7
INFO: GOOS: linux
INFO: NEXTDNS_BIN: /jffs/nextdns/nextdns
INFO: LATEST_RELEASE: 1.8.3
u) Upgrade NextDNS from 1.8.2 to 1.8.3
c) Configure NextDNS
r) Remove NextDNS
e) Exit
Choice (default=u): u
INFO: Upgrading NextDNS...
fatal error: runtime: out of memory

runtime stack:
runtime.throw(0x3a4308, 0x16)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/panic.go:1116 +0x5c fp=0xff9cf4bc sp=0xff9cf4a8 pc=0x43b80
runtime.sysMap(0xc00000, 0x400000, 0x6004a0)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/mem_linux.go:169 +0xa8 fp=0xff9cf4e0 sp=0xff9cf4bc pc=0x26b68
runtime.(*linearAlloc).alloc(0x5f1048, 0x400000, 0x400000, 0x6004a0, 0x0)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/malloc.go:1447 +0x94 fp=0xff9cf4f8 sp=0xff9cf4e0 pc=0x1d038
runtime.(*mheap).sysAlloc(0x5f0cf0, 0x400000, 0x1, 0x1)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/malloc.go:633 +0x50 fp=0xff9cf554 sp=0xff9cf4f8 pc=0x1b2e4
runtime.(*mheap).grow(0x5f0cf0, 0x1, 0x0)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/mheap.go:1344 +0x68 fp=0xff9cf590 sp=0xff9cf554 pc=0x372e8
runtime.(*mheap).allocSpan(0x5f0cf0, 0x1, 0x1e00, 0x6004b0, 0x0)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/mheap.go:1160 +0x62c fp=0xff9cf5e0 sp=0xff9cf590 pc=0x370c4
runtime.(*mheap).alloc.func1()
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/mheap.go:907 +0x50 fp=0xff9cf608 sp=0xff9cf5e0 pc=0x6def0
runtime.(*mheap).alloc(0x5f0cf0, 0x1, 0x11e, 0x0)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/mheap.go:901 +0x58 fp=0xff9cf62c sp=0xff9cf608 pc=0x36700
runtime.(*mcentral).grow(0x5f2340, 0x0)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/mcentral.go:506 +0x64 fp=0xff9cf650 sp=0xff9cf62c pc=0x2660c
runtime.(*mcentral).cacheSpan(0x5f2340, 0x1a3f4)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/mcentral.go:177 +0x440 fp=0xff9cf698 sp=0xff9cf650 pc=0x2632c
runtime.(*mcache).refill(0xf700b088, 0x1e)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/mcache.go:142 +0x9c fp=0xff9cf6ac sp=0xff9cf698 pc=0x25c70
runtime.(*mcache).nextFree(0xf700b088, 0x1e, 0x1, 0x6ccf0, 0x5ec0c0)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/malloc.go:880 +0x7c fp=0xff9cf6cc sp=0xff9cf6ac pc=0x1bacc
runtime.mallocgc(0xe0, 0x396330, 0x1, 0x1)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/malloc.go:1061 +0x798 fp=0xff9cf730 sp=0xff9cf6cc pc=0x1c40c
runtime.newobject(0x396330, 0x47c30)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/malloc.go:1195 +0x2c fp=0xff9cf744 sp=0xff9cf730 pc=0x1c850
runtime.malg(0x8000, 0x0)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/proc.go:3493 +0x1c fp=0xff9cf764 sp=0xff9cf744 pc=0x4e5e4
runtime.mpreinit(0x5ece88)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/os_linux.go:340 +0x1c fp=0xff9cf770 sp=0xff9cf764 pc=0x410d0
runtime.mcommoninit(0x5ece88, 0xffffffff, 0xffffffff)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/proc.go:663 +0x10c fp=0xff9cf798 sp=0xff9cf770 pc=0x47d84
runtime.schedinit()
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/proc.go:565 +0x84 fp=0xff9cf7c0 sp=0xff9cf798 pc=0x476e0
runtime.rt0_go(0xff9cfe17, 0xff9cfe2d, 0x0, 0xff9cfe35, 0xff9cfe41, 0xff9cfe66, 0xff9cfe7a, 0xff9cfe82, 0xff9cfead, 0xff9cfeb8, ...)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/asm_arm.s:163 +0x7c fp=0xff9cf800 sp=0xff9cf7c0 pc=0x73d0c
fatal error: runtime: out of memory

runtime stack:
runtime.throw(0x3a4308, 0x16)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/panic.go:1116 +0x5c fp=0xfffb4a5c sp=0xfffb4a48 pc=0x43b80
runtime.sysMap(0x800000, 0x400000, 0x6004a0)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/mem_linux.go:169 +0xa8 fp=0xfffb4a80 sp=0xfffb4a5c pc=0x26b68
runtime.(*linearAlloc).alloc(0x5f1048, 0x400000, 0x400000, 0x6004a0, 0x0)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/malloc.go:1447 +0x94 fp=0xfffb4a98 sp=0xfffb4a80 pc=0x1d038
runtime.(*mheap).sysAlloc(0x5f0cf0, 0x400000, 0x1, 0x1)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/malloc.go:633 +0x50 fp=0xfffb4af4 sp=0xfffb4a98 pc=0x1b2e4
runtime.(*mheap).grow(0x5f0cf0, 0x1, 0x0)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/mheap.go:1344 +0x68 fp=0xfffb4b30 sp=0xfffb4af4 pc=0x372e8
runtime.(*mheap).allocSpan(0x5f0cf0, 0x1, 0x1e00, 0x6004b0, 0x0)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/mheap.go:1160 +0x62c fp=0xfffb4b80 sp=0xfffb4b30 pc=0x370c4
runtime.(*mheap).alloc.func1()
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/mheap.go:907 +0x50 fp=0xfffb4ba8 sp=0xfffb4b80 pc=0x6def0
runtime.(*mheap).alloc(0x5f0cf0, 0x1, 0x11e, 0x0)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/mheap.go:901 +0x58 fp=0xfffb4bcc sp=0xfffb4ba8 pc=0x36700
runtime.(*mcentral).grow(0x5f2340, 0x0)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/mcentral.go:506 +0x64 fp=0xfffb4bf0 sp=0xfffb4bcc pc=0x2660c
runtime.(*mcentral).cacheSpan(0x5f2340, 0x1a3f4)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/mcentral.go:177 +0x440 fp=0xfffb4c38 sp=0xfffb4bf0 pc=0x2632c
runtime.(*mcache).refill(0xf755b088, 0x1e)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/mcache.go:142 +0x9c fp=0xfffb4c4c sp=0xfffb4c38 pc=0x25c70
runtime.(*mcache).nextFree(0xf755b088, 0x1e, 0x1, 0x6ccf0, 0x5ec0c0)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/malloc.go:880 +0x7c fp=0xfffb4c6c sp=0xfffb4c4c pc=0x1bacc
runtime.mallocgc(0xe0, 0x396330, 0x1, 0x1)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/malloc.go:1061 +0x798 fp=0xfffb4cd0 sp=0xfffb4c6c pc=0x1c40c
runtime.newobject(0x396330, 0x47c30)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/malloc.go:1195 +0x2c fp=0xfffb4ce4 sp=0xfffb4cd0 pc=0x1c850
runtime.malg(0x8000, 0x0)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/proc.go:3493 +0x1c fp=0xfffb4d04 sp=0xfffb4ce4 pc=0x4e5e4
runtime.mpreinit(0x5ece88)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/os_linux.go:340 +0x1c fp=0xfffb4d10 sp=0xfffb4d04 pc=0x410d0
runtime.mcommoninit(0x5ece88, 0xffffffff, 0xffffffff)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/proc.go:663 +0x10c fp=0xfffb4d38 sp=0xfffb4d10 pc=0x47d84
runtime.schedinit()
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/proc.go:565 +0x84 fp=0xfffb4d60 sp=0xfffb4d38 pc=0x476e0
runtime.rt0_go(0xfffb5e17, 0xfffb5e2d, 0x0, 0xfffb5e35, 0xfffb5e41, 0xfffb5e66, 0xfffb5e7a, 0xfffb5e82, 0xfffb5ead, 0xfffb5eb8, ...)
/opt/hostedtoolcache/go/1.15.1/x64/src/runtime/asm_arm.s:163 +0x7c fp=0xfffb4da0 sp=0xfffb4d60 pc=0x73d0c
i) Install NextDNS
e) Exit
Choice (default=i):

 

[Smokey613]

I had to give up on the NextDNS client on my 86U. Over the period of several days, it started consuming a lot of cpu/memory resources.

 

[Authority]

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.

Is there a way to be notified when this is updated?

 

[Mr Tvardovsky]

Is there a way to be notified when this is updated?

The only way I am aware of is through your software updater notification - in case you have a Linux PC. The updates for the Merlin client are usually synced with the updates for the Linux CLI client.

 

[RMerlin]

Is there a way to be notified when this is updated?

I believe they use Github, so you could follow their github repo to be notified when there are changes to it.