Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: nextdns.io – A Combination of Cloudflare DNS and Pi-Hole

nextdns.io

Post reply on HN
Print view View original

91–100 of 151 posts

Re: Show HN: nextdns.io – A Combination of Cloudflare DNS and Pi-Hole

#91

Post by 713233eb »

kissgyorgy wrote: post #84

There is a very important use-case which you can do on a local network but can't with this: setting up a DHCP server and pushing a default DNS server address even to clients which network settings you don't have access to, is possible locally. Xbox, streaming devices, non-geek friends devices, etc. Pihole can do this and ohmygod it's life changing!

And you can also redirect all port 53 traffic to PiHole on the gateway and let only PiHole query DNS to circumvent clients that use hardcoded IP addresses (e.g. 8.8.8.8 by default)

Re: Show HN: nextdns.io – A Combination of Cloudflare DNS and Pi-Hole

#92

Post by xfer »

yegle wrote: post #33
underwater wrote: post #28

Earlier quoted context omitted.

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.

Depending on your goal. If you just want to have an ad blocking DNS server then nextdns.io is fine. But if you also want to have some control over the privacy issue involved in using a public DNS server, you should seriously consider hosting it yourself.

You are using Google dns servers and you are saying you have "control over the privacy issue involved in using a public DNS server" ?

Re: Show HN: nextdns.io – A Combination of Cloudflare DNS and Pi-Hole

#93

Post by Proven »

savrajsingh wrote: post #86
nextdns wrote: post #2

We've been working super hard on nextdns.io, a cloud-based private DNS service that gives you full control over what is allowed or blocked on your devices. Here is a few things you can do with it: - Block malicious websites, trackers, ads, and more by combining the most popular blocklists out there, all updated in real-time (100+ lists to choose from). - Set your own privacy requirements: you decide what type of logs…

Do you support time-based blocking? Aka no reddit during working hours?

During working hours where?

Re: Show HN: nextdns.io – A Combination of Cloudflare DNS and Pi-Hole

#94

Post by 7ewis »

nextdns wrote: post #52
cromka wrote: post #47

Earlier quoted context omitted.

I am in the East Coast with 100Mbit fiber: dig @5.182.208.203 google.com ;; Query time: 390 msec

Could be a routing issue (this things need to be tweaked over time). Can you talk to us via the chat on the website so we can debug?

468ms in the UK.

9ms on Cloudflare, 10ms on Google.

Re: Show HN: nextdns.io – A Combination of Cloudflare DNS and Pi-Hole

#95

Post by petronio »

swinglock wrote: post #69
yegle wrote: post #23

I 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…

Your solution is not privacy conscious or self-hosted as long as you send all your data to Google in exchange for resolved DNS records. Why not let Unbound resolve recursively?

I think it depends on who you're trying to protect against. While using DoT to a public resolver gives the public resolver the ability to build a history of your queries, running a recursive resolver yourself means anyone who's watching the wire (ISP, local government, etc.) can build a query history instead. Some people trust Google or Cloudflare more than those other entities, or figure that Google already knows pretty well what they're up to since Analytics is pretty much everywhere and they use Gmail.

The most useful option I've seen for trying to get the benefits of both has been rotating between a list of DoT resolvers, so none get all the history and end up with fragmented profiles. There's issues there since people access the same services and thus they'll get the full list over time if the software doesn't record who got what request and stickies it to them. There's always the option of doing it over Tor, but then you're introducing multisecond latencies to your DNS queries, which isn't exactly a great experience.

Re: Show HN: nextdns.io – A Combination of Cloudflare DNS and Pi-Hole

#96

Post by blattimwind »

ignoramous wrote: post #12

Nice. DNS has grown notoriously complex over the years and it is hard work to run a standards compliant service. Congratulations. A few suggestions: - Auto-detect OS and suggest specific setup instructions right on the landing page? - The website goes blank when I block third-party JavaScript from loading. Can you please see if you can fix that? - simplednscrypt has been handy for me to DoT/DoH/DNSCrypt with AdGuard…

> Nice. DNS has grown notoriously complex over the years and it is hard work to run a standards compliant service. Congratulations.

Running your own private recursive resolver is very easy.

Edit: I believe people are confusing running a DNS nameserver with running a DNS resolver. The former might be hard, the latter is very easy.

Re: Show HN: nextdns.io – A Combination of Cloudflare DNS and Pi-Hole

#97

Post by Terretta »

kissgyorgy wrote: post #84

There is a very important use-case which you can do on a local network but can't with this: setting up a DHCP server and pushing a default DNS server address even to clients which network settings you don't have access to, is possible locally. Xbox, streaming devices, non-geek friends devices, etc. Pihole can do this and ohmygod it's life changing!

This works with this service. You can associate your public IP (your router's WAN) with a custom blocking configuration. Then you put their AnyCast IP address in your DHCP server's DNS server list. The local devices will use that address, be seen from your public IP, and get the custom config you want.

Re: Show HN: nextdns.io – A Combination of Cloudflare DNS and Pi-Hole

#99

Post by polskibus »

keybits wrote: post #64
polskibus wrote: post #61

What is the monetization plan? How have you financed the development so far?

From the OP on another reply: > 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.

Would be great if they put it high on the front page. Someone privacy-focused may be worried when he sees something privacy-oriented advertised without a business plan, which could indicate that selling data to advertisers could be the secret.

Re: Show HN: nextdns.io – A Combination of Cloudflare DNS and Pi-Hole

#100

Post by jedisct1 »

savrajsingh wrote: post #86
nextdns wrote: post #2

We've been working super hard on nextdns.io, a cloud-based private DNS service that gives you full control over what is allowed or blocked on your devices. Here is a few things you can do with it: - Block malicious websites, trackers, ads, and more by combining the most popular blocklists out there, all updated in real-time (100+ lists to choose from). - Set your own privacy requirements: you decide what type of logs…

Do you support time-based blocking? Aka no reddit during working hours?

dnscrypt-proxy can be used to securely access nextdns, and it supports time-based blocking https://github.com/jedisct1/dnscrypt-proxy/wiki/Filters#time...
Post reply on HN