Questions and Concerns regarding NextDNS current status
Dear NextDNS Team,
I'm a paying subscriber for almost a year. I really like your service and consider it to be overall better than alternatives like Control D. Sadly, the service doesn't seem to be well maintained anymore recently. It feels like only the very minimum of maintenance is being done and many issues, including critical ones, aren't addressed. The community is pretty much ignored on your Discourse forum and GitHub. Speaking of GitHub, your repositories are all inactive and unmaintained and probably out of date too. There haven't been any noticeable updates in a while. Beta features aren't developed any further and the categories stay as they are, full of harmful or outdated filter lists, a very small amount of services you can block, etc. I'm very disappointed about the current status of NextDNS and already looking for alternatives which I can use for myself and the people I care about. I hope you can explain to me why this is the case and how the near future of NextDNS looks. I would also appreciate it if more communication with the community would happen.
Kind regards
12 replies
-
I wonder if there's a way to directly get in contact with the owners of NextDNS. Perhaps through LinkedIn?
-
Feels? Evidence requested
-
I agree with you. After subscribing for about 8 years, I'm letting my subscription expire.
I'm now using Adguard Home (it's free, open source) on a Raspberry Pi. Installed using Docker.
For mobile access I use tailscale (also free for personal use)
https://github.com/AdguardTeam/AdGuardHome
https://github.com/AdguardTeam/AdGuardHome/wiki/Docker
(Another option is Pi-hole, but I have tried both and prefer ADH)
-
So I did a little digging, and for me on the US east coast, it looks like the `45.90.30.173` DNS resolver (aka `dns2.nextdns.io`) is timing out. The `45.90.28.173` (aka `dns1.nextdns.io`) resolver is fine, so I’l going to try running with just the one for a while.
I used to run my own AdGuard Home setup, but it turned out to be a fair amount of work to keep things up.
-
What made it difficult to keep up? I’m finding it to be fantastic and would have switched sooner had I known about Tailscale.
-
please open a new thread with a https://nextdns.io/diag join so we can investigate.
-
so I did that, but perhaps more important is this:
13:45:53 jeffbyrnes $ dig @45.90.30.173 example.com ; <<>> DiG 9.10.6 <<>> @45.90.30.173 example.com ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached -
same with 0 instead of 173? The diag is normal and the secondary seems to be reachable, I'm confused.
-
I mean, `.173` is the 2ndary DNS address shown to me in my.nextdns.io, so that’s why I was using it, and why it seems busted.
-
it should be the same but I’m curious to see if something is blocking this specific last byte in the IP. Can you try with .0 to see if it makes a difference. You only need .173 for link IP.
-
ah, interesting. Still busted:
15:07:57 jeffbyrnes in ~
dig @45.90.30.0 google.com ; <<>> DiG 9.10.6 <<>> @45.90.30.0 google.com
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached
-
-
I posted a reply with a bunch of resources for Pi-Hole and Pi-Hole alternatives and it all got deleted :(
Content aside
-
4
Likes
- 4 hrs agoLast active
- 12Replies
- 382Views
-
8
Following