NextDNS Installer

[Olivier Poitrey]

How can it use so much memory when most routers don't even have that much? My AC87U shows 140MB of RAM is used out of 256MB available. That's the total figure on the status page. And I'm really hammering it with torrents this moment...

You are reading the wrong value. RSS is the actual memory used by the process. NextDNS client uses Go, and Go memory allocator pre-allocates large chucks of virtual memory to avoid frequent syscalls to allocate memory (it is slow). Allocated memory won’t take RAM until something is stored in it.

 

[maghuro]

Hey Olivier,
Why is nextdns client on my Ac86u spamming the log so much?
Each minute I receive a line like those:

nextdns[15924]: Connected 185.93.182.43:443 (con=59ms tls=90ms, TLS13)
Mar 18 03:44:18 nextdns[15924]: Connected 185.93.182.43:443 (con=74ms tls=89ms, TLS13)
Mar 18 03:44:52 nextdns[15924]: Connected 185.93.182.43:443 (con=82ms tls=104ms, TLS13)
Mar 18 03:46:19 nextdns[15924]: Connected 185.93.182.43:443 (con=65ms tls=90ms, TLS13)
Mar 18 03:47:19 nextdns[15924]: Connected 185.93.182.43:443 (con=66ms tls=89ms, TLS13)
Mar 18 03:48:20 nextdns[15924]: Connected 185.93.182.43:443 (con=68ms tls=90ms, TLS13)
Mar 18 03:48:52 nextdns[15924]: Connected 185.93.182.43:443 (con=75ms tls=91ms, TLS13)
Mar 18 03:50:00 nextdns[15924]: Connected 185.93.182.43:443 (con=0ms tls=0ms, )
Mar 18 03:50:05 DNSOMatic: Nothing to update. Current IP: 95.69.59.254
Mar 18 03:50:48 nextdns[15924]: Connected 185.93.182.43:443 (con=66ms tls=115ms, TLS13)
Mar 18 03:52:09 nextdns[15924]: Connected 185.93.182.43:443 (con=80ms tls=87ms, TLS13)
Mar 18 03:53:21 nextdns[15924]: Connected 185.93.182.43:443 (con=118ms tls=137ms, TLS13)
Mar 18 03:55:36 nextdns[15924]: Connected 185.93.182.43:443 (con=63ms tls=91ms, TLS13)
Mar 18 03:56:22 nextdns[15924]: Connected 185.93.182.43:443 (con=73ms tls=86ms, TLS13)
Mar 18 03:57:23 nextdns[15924]: Connected 185.93.182.43:443 (con=82ms tls=88ms, TLS13)
Mar 18 03:58:23 nextdns[15924]: Connected 185.93.182.43:443 (con=69ms tls=88ms, TLS13)
Mar 18 04:00:00 nextdns[15924]: Connected 185.93.182.43:443 (con=0ms tls=0ms, TLS13

 

[Smokey613]

It does the same thing on mine. I guess it likes to be “chatty”.

 

[maghuro]

I will absolutely buy the paid version when it comes out of beta. Perfect job!!!
@Olivier Poitrey , are you planing to have a server in Portugal?
Nearest server to my right now is Spain, and I can perfectly notice the difference between cloudflare and nextdns lookups!

Also - my RT86U is armv8, and when installing it shows armv7

 

[Olivier Poitrey]

I will absolutely buy the paid version when it comes out of beta. Perfect job!!!
@Olivier Poitrey , are you planing to have a server in Portugal?
Nearest server to my right now is Spain, and I can perfectly notice the difference between cloudflare and nextdns lookups!

Yes we will add PoPs as we grow.

 

[maghuro]

Yes we will add PoPs as we grow.

Best wishes! You're the best

 

[maghuro]

It does the same thing on mine. I guess it likes to be “chatty”.

"Chatty" is very simillar to a portuguese word "Chato", which means "Annoying", which I think it's the case!

 

[maghuro]

@Olivier Poitrey - suggestion: if a custom name has been defined by user for some device, report that name instead on the real device name.
I have some devices connected with strange names that I've manually named on router. But the name sent to NextDNS is the "strange" name.
Thanks

 

[Olivier Poitrey]

@Olivier Poitrey - suggestion: if a custom name has been defined by user for some device, report that name instead on the real device name.
I have some devices connected with strange names that I've manually named on router. But the name sent to NextDNS is the "strange" name.
Thanks

It will be the case.

 

[maghuro]

It will be the case.

Right now it isn't reporting the custom name that I defined, but the original name of the device.

 

[SushiGodzilla]

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?

 

[maghuro]

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?

Portugal, car*lho

Back to topic,i how do you know servers ip to tracert them?
Unfortunately is the closest server to us. Hoping nextdns grow and have server in Portugal too...

Also, @Olivier Poitrey
Is it possible to install this script over Asus original firmware?

 

[maghuro]

Portugal, car*lho

Back to topic,i how do you know servers ip to tracert them?
Unfortunately is the closest server to us. Hoping nextdns grow and have server in Portugal too...

Also, @Olivier Poitrey
Is it possible to install this script over Asus original firmware?

ping @Olivier Poitrey

 

[SomeWhereOverTheRainBow]

ping @Olivier Poitrey

what is best in life?
ping @Olivier Poitrey

 

[maghuro]

what is best in life?
ping @Olivier Poitrey

Sorry, didn't understand

 

[SushiGodzilla]

@Olivier Poitrey Thanks for the server in Portugal. It works much better now!

 

[maghuro]

@Olivier Poitrey Thanks for the server in Portugal. It works much better now!

Indeed!
However, using Androids DNS privacy, it still connects to Madrid

 

[iJorgen]

Saw that a new version 1.5.1 out now. Some interesting caching-features added to check out.

  -cache-size string
        Set the size of the cache in byte. Use 0 to disable caching. The value
        can be expressed with unit like kB, MB, GB. The cache is automatically
        flushed when the pointed configuration is updated. (default "0")

  -cache-max-age duration
        If set to greater than 0, a cached entry will be considered stall after
        this duration, even if the record's TTL is higher.

  -max-ttl duration
        If set to greater than 0, defines the maximum TTL value that will be
        handed out to clients. The specified maximum TTL will be given to
        clients instead of the true TTL value if it is lower. The true TTL
        value is however kept in the cache to evaluate cache entries
        freshness. This is best used in conjunction with the cache to force
        clients not to rely on their own cache in order to pick up
        configuration changes faster.

 

[maghuro]

Indeed!
However, using Androids DNS privacy, it still connects to Madrid

Update - server in Portugal doesn't have anycast yet. You can only connect using nextdns official apps.
They're still testing this new pop

 

[SushiGodzilla]

Update - server in Portugal doesn't have anycast yet. You can only connect using nextdns official apps.
They're still testing this new pop

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?