How do you make money? How can I make sure you won't sell my data?
Show HN: nextdns.io – A Combination of Cloudflare DNS and Pi-Hole
21–30 of 151 posts
Re: Show HN: nextdns.io – A Combination of Cloudflare DNS and Pi-Hole
#22Very nice. I’ve been annoyed opendns hasn’t done similar and hoping something like this would come around.
Them getting bought by Cisco has greatly hindered their ability to innovate and stay current I guess.
Re: Show HN: nextdns.io – A Combination of Cloudflare DNS and Pi-Hole
#23I don't understand why any privacy conscious person would choose a hosted service instead of self-hosting your own solution.
Implementing the whole thing (modulo the anycast IP, which is the only thing I did not use) is easy. I have a docker-compose file which does the whole stack:
1. Unbound DNS which provides DNS-over-TLS service at port 853. It forward request to my local pihole's 53 port. 2. Pihole forward request to my Stubby DNS server. 3. Stubby connects to Google DNS over DNS-over-TLS. 4. A separate docker container to run certbot to update certificate used by the unbound container. 5. A separate docker container with Pomerium as reverse proxy so I can remote access PiHole UI.
Then you can configure your Android phone to use your unbound DNS server as the "private DNS" server. I've being using this setup for more than a month and works really well.
UPDATE: I posted my docker-compose.yaml file at https://github.com/yegle/your-dns. I'll update the README soon.
Re: Show HN: nextdns.io – A Combination of Cloudflare DNS and Pi-Hole
#24How do you make money? How can I make sure you won't sell my data?
The service is free during beta, then freemium with low pricing tiers (something like free up to 500,000 DNS queries a month, then $0.99/month). We will tweak later based on actual costs at scale, but it will follow this logic.
Selling data is against what we believe in and would also be counter-productive (everybody would stop using the service instantly).
Re: Show HN: nextdns.io – A Combination of Cloudflare DNS and Pi-Hole
#25I don't understand why any privacy conscious person would choose a hosted service instead of self-hosting your own solution. Implementing the whole thing (modulo the anycast IP, which is the only thing I did not use) is easy. I have a docker-compose file which does the whole stack: 1. Unbound DNS which provides DNS-over-TLS service at port 853. It forward request to my local pihole's 53 port. 2. Pihole forward reques…
Could you share your compose file or the images you're using?
Re: Show HN: nextdns.io – A Combination of Cloudflare DNS and Pi-Hole
#26Be advised: pi-hole ignores security issues in their product. https://github.com/pi-hole/pi-hole/issues/2704
I’ve been a security professional for 20+ years and I agree with them. You’re complaining about an attack surface that would be more easily explored in a bunch of different ways.
I’m not sure why you bring this up on every post vaguely related to pi-hole.
Re: Show HN: nextdns.io – A Combination of Cloudflare DNS and Pi-Hole
#27I don't understand why any privacy conscious person would choose a hosted service instead of self-hosting your own solution. Implementing the whole thing (modulo the anycast IP, which is the only thing I did not use) is easy. I have a docker-compose file which does the whole stack: 1. Unbound DNS which provides DNS-over-TLS service at port 853. It forward request to my local pihole's 53 port. 2. Pihole forward reques…
A sidenote -- Anycast is trivially easy to setup; with their current host, Vultr, offering essentially turn-key solutions.
Re: Show HN: nextdns.io – A Combination of Cloudflare DNS and Pi-Hole
#28I don't understand why any privacy conscious person would choose a hosted service instead of self-hosting your own solution. Implementing the whole thing (modulo the anycast IP, which is the only thing I did not use) is easy. I have a docker-compose file which does the whole stack: 1. Unbound DNS which provides DNS-over-TLS service at port 853. It forward request to my local pihole's 53 port. 2. Pihole forward reques…
You just answered your own question. A self hosted solution requires a lot of domain and technical knowledge to set up. To you it might seem trivial, but that's an insurmountable barrier to many.
This project seems to occupy the same niche as products like Blokada. Most of the benefits of a self hosted solution, with a much lower barrier to entry.
Re: Show HN: nextdns.io – A Combination of Cloudflare DNS and Pi-Hole
#29Be advised: pi-hole ignores security issues in their product. https://github.com/pi-hole/pi-hole/issues/2704
Just to know, this isn't using Pi-Hole (from what I understand). This is a "Pi-Hole-like" service.
Re: Show HN: nextdns.io – A Combination of Cloudflare DNS and Pi-Hole
#30Personally I run either pihole or something similar however setting something similar for all the friends is a bit cumbersome as it at least requires getting a raspberry pi. This seems like a really intriguing alternative although will voice similar concerns as others are expressing that the site does not indicate the source of the funding, motivations for the project, etc. As such that could be a barrier to entrust…
Motivations: like most tech startups, scratching your own itch :) Funding: Free during beta, then freemium with low pricing tiers (something like free up to 500,000 DNS queries a month, then $0.99/month). We will tweak later based on actual costs at scale, but it will follow this logic.
I wouldn't know if 500k is a little or a lot.