NextDNS Installer

[maghuro]

Fine for me. I'm using the official apps in my Apple devices and the script for my Asus Router.
Are you not using the script for your Asus router?

Using apps it connects to Portugal server. Anycast isn't supported yet, as they're looking for a better partner here.

 

[maghuro]

New PoP locations: Austria and Belgium!
https://headwayapp.co/nextdns-changelog

 

[nixballs]

@Olivier Poitrey - thanks for the NextDNS - truly useful service and very nicely integrated.

• I have been intermittently using the NextDNS macOS App and seems to be working really well.
• Today I decided to install the AsusWRT client.
• I can see many screenshots/questions regarding what settings should be set at the WAN page.
• I also saw few recommendations from @RMerlin regarding DNS entries / no DNS will only cause issues - which it definitely makes sense.
• Given the two need to co-exist, can you please provide the recommended WAN settings on the first page so that everyone follows what you recommend or how NextDNS is supposed to work with AsusWRT?

Once again, thanks for NextDNS!

Cheers,
Ivan

 

[chris.at]

After updating to the latest version my log is filling with this messages:

nextdns[416]: Discovery: clientList: : invalid format: missing item separator

Any idea whats wrong?

KR, Chris

 

[dave14305]

After updating to the latest version my log is filling with this messages:

nextdns[416]: Discovery: clientList: : invalid format: missing item separator

Any idea whats wrong?

KR, Chris

What firmware version? What’s the output of this command:

nvram get custom_clientlist

Does it start with a < character?

 

[chris.at]

What firmware version?

Router firmware didn't change, 384.16. But nextdns got updated yesterday, 1.5.2.

What’s the output of this command:

nvram get custom_clientlist

Does it start with a < character?

No, it's empty at all:

admin@router:/tmp/home/root# nvram get custom_clientlist

admin@router:/tmp/home/root# nvram show | grep clientlist
custom_clientlist=

Maybe because I never made a custom clientlist, seems like this situation is not handled properly with the latest nextdns update?

 

[dave14305]

Router firmware didn't change, 384.16. But nextdns got updated yesterday, 1.5.2.


No, it's empty at all:

admin@router:/tmp/home/root# nvram get custom_clientlist

admin@router:/tmp/home/root# nvram show | grep clientlist
custom_clientlist=

Maybe because I never made a custom clientlist, seems like this situation is not handled properly with the latest nextdns update?

Is it empty or just blanks (non-empty)? Try

nvram get custom_clientlist > nvclientlist.txt
nvram set custom_clientlist=
nvram commit
ls -l nvclientlist.txt

The file size is hopefully no larger than 1 byte.

 

[chris.at]

admin@router:/jffs# ls -l nvclientlist.txt
-rw-rw-rw- 1 admin root 1 Apr 19 14:45 nvclientlist.txt

So, it's empty.

 

[dave14305]

admin@router:/jffs# ls -l nvclientlist.txt
-rw-rw-rw- 1 admin root 1 Apr 19 14:45 nvclientlist.txt

So, it's empty.

You can either make a minor change in your Client List to populate it as a workaround, or report the bug on Github to @Olivier Poitrey

 

[chris.at]

Well, better to report the bug to get it fixed for everyone, not only me. Will see how to do this on github, never used before. Thank you for helping investigate the cause!

Maybe Olivier also reads it in this thread.

 

[Olivier Poitrey]

Hi. Another happy user from Portugal here. Thanks @Olivier Poitrey for the awesome service.

During the evening my Asus router reports traceroute pings over 141 ms to Madrid server. The lag is sometimes noticeable, is there something I can do? Perhaps increase the router's DNS cache?

The cli should go to the portugal server. Why are you tracerouting madrid?

 

[Olivier Poitrey]

Well, better to report the bug to get it fixed for everyone, not only me. Will see how to do this on github, never used before. Thank you for helping investigate the cause!

Maybe Olivier also reads it in this thread.

It’s always better to report issues on github. I don’t always get notifications from this forum.

 

[maghuro]

It’s always better to report issues on github. I don’t always get notifications from this forum.

https://github.com/nextdns/nextdns/issues/165

 

[SushiGodzilla]

The cli should go to the portugal server. Why are you tracerouting madrid?

Hello,
That was before you deployed the Portuguese server. Now the ping is 4ms. Much better!

 

[maghuro]

Hello,
That was before you deployed the Portuguese server. Now the ping is 4ms. Much better!

4ms OMG teach me how, master...
50ms here

 

[CrendKing]

What's the benefit of installing the service with installer on the router versus changing dnsmasq.conf and stubby.yml as instructed in the setup page? Cache?

BTW, when I used the nextdns service, from time to time google.com just become unresolved until like 10 seconds passed or manually restart the service. Never happened again after I uninstall the service. I suppose the caching has some bug? Is it known issue?

 

[jim trudel]

with that dns and doT option, with stubby, I receive many warning in my router's log about possible dns rebind attack.... It was not like that with the other dns resolvers. I think the cause is about the next dns setup page, in config, there is a protection against rebind.....

 

[Hugga Wugga]

The service seems to work well... apart from the blocking of proxy sites to bypass it. I tested 10 sites and 9 of them were allowed through. This could be solved quite easily if you allowed wildcards in the blacklist section as all 10 sites had the words 'unblock' or 'proxy' in the domain name. I think I'd need to use something in addition - an extra layer - that supports this.

 

[maghuro]

Please use GitHub issues tracker, as Olivier said, he doesn't come here often.

 

[jim trudel]

Please use GitHub issues tracker, as Olivier said, he doesn't come here often.

Are you addressing to me?

If so, do you have a link?
Thanks

Envoyé de mon SM-G960W en utilisant Tapatalk