profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/nextdns/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
NextDNS nextdns https://nextdns.io The next-generation DNS service.

nextdns/nextdns 1386

NextDNS CLI client (DoH Proxy)

nextdns/metadata 357

This repository contains the data behind our Security, Privacy and Parental Control features.

nextdns/cname-cloaking-blocklist 99

A list of domains used by tracking companies as CNAME destination when disguising third-party trackers as first-party trackers.

nextdns/windows 58

Windows client for NextDNS

nextdns/diag 52

Network diagnostic tool

issue closednextdns/nextdns

No Option To Exclude WiFi Networks in iOS 15 or iPadOS 15

Context

  • Version: 2.0.1(29)
  • Platform: iOS

<Describe the bug>

On a fresh install of iOS 15 there is no option given in the settings to exclude certain WiFi networks. Is this a known bug and will it be fixed with an update?

closed time in 26 minutes

argiedoubleya

issue commentnextdns/nextdns

No Option To Exclude WiFi Networks in iOS 15 or iPadOS 15

This is a bug in iOS. Apple said they will fix it in a future revision.

Closing as this is not related to CLI.

argiedoubleya

comment created time in 26 minutes

issue openednextdns/nextdns

No Option To Exclude WiFi Networks in iOS 15 or iPadOS 15

Context

  • Version: 2.0.1(29)
  • Platform: iOS

<Describe the bug>

On a fresh install of iOS 15 there is no option given in the settings to exclude certain WiFi networks. Is this a known bug and will it be fixed with an update?

created time in an hour

startednextdns/nextdns

started time in 13 hours

fork MeatsMountain/windows

Windows client for NextDNS

fork in a day

startednextdns/windows

started time in a day

issue commentnextdns/nextdns

OpenWRT 19.07.8 deadline exceeded

root@OpenWrt:~# curl -v https://dns.nextdns.io/info
> GET /info HTTP/1.1
> Host: dns.nextdns.io
> User-Agent: curl/7.66.0
> Accept: */*
> 
< HTTP/1.1 200 OK
< Access-Control-Allow-Origin: *
< Content-Type: application/json
< Strict-Transport-Security: max-age=63072000; includeSubDomains; preload
< Timing-Allow-Origin: *
< Date: Fri, 17 Sep 2021 04:56:45 GMT
< Content-Length: 85
< 
{"locationName": "🇨🇿 Prague, Czech Republic", "pop": "zepto-prg", "rtt": 30588}root@OpenWrt:~# 
crssi

comment created time in 2 days

fork ymn/windows

Windows client for NextDNS

fork in 2 days

issue commentnextdns/nextdns

OpenWRT 19.07.8 deadline exceeded

Please show the output of curl -v https://dns.nextdns.io/info

crssi

comment created time in 2 days

issue commentnextdns/nextdns

OpenWRT 19.07.8 deadline exceeded

It was disabled...

image image

crssi

comment created time in 2 days

issue commentnextdns/nextdns

deadline exceeded

Today internet was completely down Had to restart the router. . Last login: Sun Sep 12 14:20:11 CEST 2021 on pts/0 Linux EdgeRouter 4.14.54-UBNT #1 SMP Tue May 11 13:23:28 UTC 2021 mips Welcome to EdgeOS peter@EdgeRouter:~$ sudo nextdns restart Error: /config/scripts/post-config.d/nextdns.sh restart: exit status 1: peter@EdgeRouter:~$ sudo nextdns stop Error: /config/scripts/post-config.d/nextdns.sh stop: signal: killed: peter@EdgeRouter:~$ sudo nextdns start Error: /config/scripts/post-config.d/nextdns.sh start: signal: killed: peter@EdgeRouter:~$ reboot now

i will do the diag when the problem reoccurs

deman3417

comment created time in 2 days

issue commentnextdns/nextdns

OpenWRT 19.07.8 deadline exceeded

Can you please disable nextdns before running the diag?

crssi

comment created time in 2 days

issue commentnextdns/nextdns

OpenWRT 19.07.8 deadline exceeded

Note: on each step 2 I have replaced 2nd chunk in the IP for xxx (privacy). Thank you Cheers

Testing IPv6 connectivity
  available: false
Fetching https://test.nextdns.io
  Fetch error: Get "https://test.nextdns.io": unexpected EOF
Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io)
Fetch error: Get "https://dns.nextdns.io/info": EOF
Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io)
Fetch error: Get "https://dns.nextdns.io/info": EOF
Fetching PoP name for anycast primary IPv4 (45.90.28.0)
Fetch error: Get "https://dns.nextdns.io/info": EOF
Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
Fetch error: Get "https://dns.nextdns.io/info": EOF
Pinging PoPs
  edis-lju: 10.93ms
  anexia-lju: 8.382ms
  exoscale-vie: 14.605ms
  edis-bud: 25.434ms
  anexia-bts: 21.623ms
  exoscale-muc: 20.509ms
  edis-zag: 26.469ms
  anexia-muc: 26.572ms
  anexia-vie: 34.689ms
  anexia-bud: 47.897ms
Traceroute for ultra low latency primary IPv4 (37.252.224.3)
    1    192.168.0.1    1ms   1ms   0ms
    2     77.xxx.8.1   11ms   9ms   9ms
    3   217.72.74.25    9ms  11ms  10ms
    4   91.220.194.8    7ms   8ms   9ms
    5  212.103.153.2    7ms  10ms  11ms
    6   37.252.224.3    8ms   9ms   9ms
Traceroute for ultra low latency secondary IPv4 (192.71.244.126)
    1    192.168.0.1    0ms   0ms   0ms
    2     77.xxx.8.1    8ms  10ms  11ms
    3    77.38.11.45    9ms  11ms   8ms
    4 185.66.149.236   12ms   7ms  10ms
    5  185.66.148.89    9ms  10ms  10ms
    6  195.206.228.3   12ms   9ms  11ms
    7 192.71.244.126   10ms  16ms   9ms
Traceroute for anycast primary IPv4 (45.90.28.0)
    1    192.168.0.1    0ms   0ms   0ms
    2     77.xxx.8.1    *    10ms  10ms
    3    77.38.11.45    9ms   9ms  10ms
    4 185.66.149.146   11ms   8ms  12ms
    5  185.66.149.52   12ms  10ms   9ms
    6 82.117.193.164   21ms  25ms  22ms
    7    89.216.5.97   31ms  33ms  33ms
    8    89.216.5.97   47ms  34ms  32ms
    9                   *     *     *
   10     45.90.28.0   32ms  31ms  32ms
Traceroute for anycast secondary IPv4 (45.90.30.0)
    1    192.168.0.1    0ms   0ms   0ms
    2     77.xxx.8.1    9ms  10ms  17ms
    3    77.38.11.45    9ms  11ms  10ms
    4 185.66.149.146   12ms  12ms  15ms
    5  185.66.149.52   10ms   9ms  10ms
    6 82.117.193.164   27ms  24ms  24ms
    7    89.216.5.78   32ms  29ms  22ms
    8    89.216.5.78   24ms  26ms  25ms
    9    91.206.52.5   33ms  31ms  35ms
   10     45.90.30.0   32ms  33ms  36ms
crssi

comment created time in 2 days

issue commentnextdns/nextdns

OpenWRT 19.07.8 deadline exceeded

Ssh the router and run sh -c 'sh -c "$(curl -s https://nextdns.io/diag)"'

crssi

comment created time in 2 days

issue commentnextdns/metadata

NSABlocklist

The whole blacklist doesn’t make sense See https://github.com/nextdns/metadata/pull/507

3xploiton3

comment created time in 2 days

startednextdns/nextdns

started time in 2 days

issue commentnextdns/nextdns

OpenWRT 19.07.8 deadline exceeded

Not sure what you mean exactly... to run this from a computer that is connected to the route or to run this directly on the router? In case of latter, I am not sure how can I do that. 😢

Cheers

crssi

comment created time in 2 days

issue commentnextdns/nextdns

deadline exceeded

Can you please run a https://nextdns.io/diag from the router?

deman3417

comment created time in 2 days

issue commentnextdns/nextdns

OpenWRT 19.07.8 deadline exceeded

Can you please run a https://nextdns.io/diag from this router?

crssi

comment created time in 2 days

issue openednextdns/metadata

NSABlocklist

https://github.com/CHEF-KOCH/NSABlocklist is not available

change to

https://github.com/shyamsantoki/nsablocklist

created time in 2 days

issue commentnextdns/nextdns

Mac OS client - Catalina - with VPN client

I still get this issue with the CLI client on macOS. When I connect to a VPN (in my case ExpressVPN and SurfShark) it overrides DNS resolution.

krioso

comment created time in 2 days

issue commentnextdns/nextdns

OpenWRT 19.07.8 deadline exceeded

Actually nothing... its a router in the apartment of my folks and they do not have any technical means even to access the config and I haven't touched it for months.

Two days ago it suddenly stopped working with last entry in NextDNS log at Tuesday, September 14, 2021 9:38 PM CET.

I though that is was OpenWRT problem since until yesterday it was on version 19.07.7 with NextDNS 1.32.xx (xx is what I don't remember), it was the last version at the time the router was touched the last time.

So yesterday I have upgraded it to up-to-date to make it work again... unfortunately that didn't help.

Cheers

crssi

comment created time in 3 days

push eventnextdns/metadata

x

commit sha 7a158c3cf3523004764310fe7a0202c2c1094c33

ti feeds: remove revil domains (mostly decoys)

view details

push time in 3 days

issue commentnextdns/nextdns

OpenWRT 19.07.8 deadline exceeded

Is this a new problem on this router? If yes, what changed since last time it worked?

crssi

comment created time in 3 days

issue openednextdns/nextdns

OpenWRT 19.07.8 deadline exceeded

Context

  • CLI Version: 1.37.2-1
  • Platform: OpenWRT 19.07.8
daemon.notice nextdns[2520]: Starting NextDNS 1.37.2/linux on 127.0.0.1:5342
daemon.notice nextdns[2520]: Listening on TCP/127.0.0.1:5342
daemon.notice nextdns[2520]: Starting mDNS discovery
daemon.notice nextdns[2520]: Listening on UDP/127.0.0.1:5342
daemon.notice nextdns[2520]: Setting up router
daemon.notice nextdns[2520]: Query 192.168.1.181 UDP A ac.duckduckgo.com. (qry=68/res=12) 5116ms : doh resolve: context deadline exceeded
daemon.notice nextdns[2520]: Received signal: broken pipe (ignored)
daemon.warn nextdns[2520]: Endpoint provider failed: &{dns.nextdns.io https://dns.nextdns.io#45.90.28.0,2a07:a8c0::,45.90.30.0,2a07:a8c1::}: exchange: roundtrip: unexpected EOF
daemon.warn nextdns[2520]: Endpoint provider failed: &{dns.nextdns.io https://dns.nextdns.io}: exchange: roundtrip: dial tcp: lookup dns.nextdns.io on 127.0.0.1:53: read udp 127.0.0.1:37758->127.0.0.1:53: i/o timeout
daemon.warn nextdns[2520]: Endpoint failed: https://dns1.nextdns.io#45.90.28.0,2a07:a8c0::: roundtrip: context deadline exceeded
daemon.notice nextdns[2520]: Received signal: terminated
daemon.notice nextdns[2520]: Stopping NextDNS 1.37.2/linux
daemon.notice nextdns[2520]: Restore router settings
daemon.warn nextdns[2520]: Endpoint failed: https://dns2.nextdns.io#45.90.30.0,2a07:a8c1::: roundtrip: context deadline exceeded
daemon.notice nextdns[2520]: Switching endpoint: 45.90.28.0:53
daemon.notice nextdns[2520]: Query 192.168.1.181 UDP A ac.duckduckgo.com. (qry=68/res=12) 38235ms UDP: dns resolve: dial: dial udp 45.90.28.0:53: i/o timeout
daemon.notice nextdns[2520]: Query 192.168.1.181 UDP A ac.duckduckgo.com. (qry=68/res=12) 37223ms UDP: dns resolve: dial: dial udp 45.90.28.0:53: i/o timeout
daemon.notice nextdns[2520]: Query 192.168.1.181 UDP A my.nextdns.io. (qry=64/res=12) 36602ms UDP: dns resolve: dial: dial udp 45.90.28.0:53: i/o timeout
daemon.notice nextdns[2520]: Query 192.168.1.181 UDP A my.nextdns.io. (qry=64/res=12) 36561ms UDP: dns resolve: dial: dial udp 45.90.28.0:53: i/o timeout
daemon.notice nextdns[2520]: Query 192.168.1.181 UDP A my.nextdns.io. (qry=64/res=12) 35589ms UDP: dns resolve: dial: dial udp 45.90.28.0:53: i/o timeout
daemon.notice nextdns[2520]: Query 192.168.1.181 UDP A ac.duckduckgo.com. (qry=68/res=12) 35213ms UDP: dns resolve: dial: dial udp 45.90.28.0:53: i/o timeout
daemon.notice nextdns[2520]: Query 192.168.1.181 UDP A my.nextdns.io. (qry=64/res=12) 33595ms UDP: dns resolve: dial: dial udp 45.90.28.0:53: i/o timeout
daemon.notice nextdns[2520]: Query 192.168.1.181 UDP A ac.duckduckgo.com. (qry=68/res=12) 31198ms UDP: dns resolve: dial: dial udp 45.90.28.0:53: i/o timeout
daemon.notice nextdns[2520]: Query 192.168.1.181 UDP A my.nextdns.io. (qry=64/res=12) 29581ms UDP: dns resolve: dial: dial udp 45.90.28.0:53: i/o timeout
daemon.notice nextdns[2520]: Query 192.168.1.181 UDP A ac.duckduckgo.com. (qry=68/res=12) 27175ms UDP: dns resolve: dial: dial udp 45.90.28.0:53: i/o timeout
daemon.notice nextdns[2520]: Query 192.168.1.181 UDP A ac.duckduckgo.com. (qry=68/res=12) 27183ms UDP: dns resolve: dial: dial udp 45.90.28.0:53: i/o timeout
daemon.notice nextdns[2520]: Query 192.168.1.181 UDP A ac.duckduckgo.com. (qry=68/res=12) 26167ms UDP: dns resolve: dial: dial udp 45.90.28.0:53: i/o timeout
daemon.notice nextdns[2520]: Query 192.168.1.181 UDP A my.nextdns.io. (qry=64/res=12) 25593ms UDP: dns resolve: dial: dial udp 45.90.28.0:53: i/o timeout
daemon.notice nextdns[2520]: Query 192.168.1.181 UDP A my.nextdns.io. (qry=64/res=12) 25583ms UDP: dns resolve: dial: dial udp 45.90.28.0:53: i/o timeout
daemon.notice nextdns[2520]: Query 192.168.1.181 UDP A my.nextdns.io. (qry=64/res=12) 24585ms UDP: dns resolve: dial: dial udp 45.90.28.0:53: i/o timeout
daemon.notice nextdns[2520]: Query 192.168.1.181 UDP A ac.duckduckgo.com. (qry=68/res=12) 24217ms UDP: dns resolve: dial: dial udp 45.90.28.0:53: i/o timeout
daemon.notice nextdns[2520]: Query 192.168.1.181 UDP A my.nextdns.io. (qry=64/res=12) 22523ms UDP: dns resolve: dial: dial udp 45.90.28.0:53: i/o timeout
daemon.notice nextdns[2520]: Query 127.0.0.1 UDP AAAA dns.nextdns.io. (qry=55/res=12) 20383ms UDP: dns resolve: dial: dial udp 45.90.28.0:53: i/o timeout
daemon.notice nextdns[2520]: Query 127.0.0.1 UDP A dns.nextdns.io. (qry=55/res=12) 20384ms UDP: dns resolve: dial: dial udp 45.90.28.0:53: i/o timeout
daemon.notice nextdns[2520]: Query 192.168.1.181 UDP A ac.duckduckgo.com. (qry=68/res=12) 20262ms UDP: dns resolve: dial: dial udp 45.90.28.0:53: i/o timeout
daemon.notice nextdns[2520]: Query 192.168.1.181 UDP A my.nextdns.io. (qry=64/res=12) 18616ms UDP: dns resolve: dial: dial udp 45.90.28.0:53: i/o timeout
daemon.notice nextdns[2520]: Query 127.0.0.1 UDP AAAA dns.nextdns.io. (qry=55/res=12) 15406ms UDP: dns resolve: dial: dial udp 45.90.28.0:53: i/o timeout
daemon.notice nextdns[2520]: Query 127.0.0.1 UDP A dns.nextdns.io. (qry=55/res=12) 15403ms UDP: dns resolve: dial: dial udp 45.90.28.0:53: i/o timeout
daemon.info procd: Instance nextdns::instance1 pid 2520 not stopped on SIGTERM, sending SIGKILL instead
daemon.notice nextdns[2759]: Starting NextDNS 1.37.2/linux on 127.0.0.1:5342
daemon.notice nextdns[2759]: Listening on TCP/127.0.0.1:5342
daemon.notice nextdns[2759]: Starting mDNS discovery
daemon.notice nextdns[2759]: Listening on UDP/127.0.0.1:5342
daemon.notice nextdns[2759]: Setting up router
daemon.info procd: Instance nextdns::instance1 pid 2759 not stopped on SIGTERM, sending SIGKILL instead
daemon.notice nextdns[2984]: Starting NextDNS 1.37.2/linux on 127.0.0.1:5342
daemon.notice nextdns[2984]: Listening on TCP/127.0.0.1:5342
daemon.notice nextdns[2984]: Starting mDNS discovery
daemon.notice nextdns[2984]: Listening on UDP/127.0.0.1:5342
daemon.notice nextdns[2984]: Setting up router
daemon.warn nextdns[2984]: Endpoint provider failed: &{dns.nextdns.io https://dns.nextdns.io#45.90.28.0,2a07:a8c0::,45.90.30.0,2a07:a8c1::}: exchange: roundtrip: unexpected EOF

Please advise.

Cheers

created time in 3 days

startednextdns/metadata

started time in 3 days

issue commentnextdns/nextdns

Ubiquiti UDMP Problem with Updating

this worked: add repo after unifi-os shell. then exit shell and run nextdns upgrade - that got it to install and run.

This also worked for me @rs

And for me too...

Veldkornet

comment created time in 3 days

issue commentnextdns/nextdns

deadline exceeded

Strange. Problem started with the upgrade from 1.36.0 to 1.37.2 Internetconnection is 24/7 alive since more than a year.

deman3417

comment created time in 3 days

issue commentnextdns/nextdns

Ubiquiti UDMP Problem with Updating

Thank you for the info janthony6 made the change.

Veldkornet

comment created time in 4 days

fork yummy-ja/metadata

This repository contains the data behind our Security, Privacy and Parental Control features.

https://nextdns.io

fork in 4 days