Chromium's Impact on Root DNS Traffic

Re:Chromium's Impact on Root DNS Traffic by vetinari on Friday August 21, 2020 @07:14PM (#24239892)

I still don't understand what's nextdns.io doing in the stack.

Couldn't you just run your recursive resolver as recursive resolver and let it ask respective authoritative servers directly, instead of forwarding to the middleman? You can run your own blocklists on your unbound/kresd/whatever.

Then DNS servers out on the Internet are queried by some random IP from a VPS/EC2/VM IP range, so they are about as wise as when queried by nextdns.io.

[ Parent | on HN ]

Re:Chromium's Impact on Root DNS Traffic by rsync on Friday August 21, 2020 @07:37PM (#24240028)

Yes, of course nextdns is not required - I simply added it because that is my own setup and it adds the pihole-like ad-blocking to the workflow.

They are my favorite IaaS startup of the last 5-10 years - it is a genius idea and I wish I had thought of it.

[ Parent | on HN ]