News for hackers. Stuff that matters.
Re:Choosing a Public DNS Resolver by kev009 on Saturday June 27, 2026 @10:50PM (#48703886)
I always just set up root recursors at my home and other locations. I've never noticed any downside.
Re:Choosing a Public DNS Resolver by icedchai on Saturday June 27, 2026 @10:58PM (#48703927)
Same. I’ve been running my own caching DNS servers since my earliest home network, dating back almost 30 years.
Re:Choosing a Public DNS Resolver by colinsane on Sunday June 28, 2026 @02:16AM (#48704883)
the _one_ downside i've seen is on an airplane serviced by Starlink: UDP was extremely lossy to the point that whatever recursive resolver i was using at the time would mark half of all nameservers it saw as "unhealthy" and start returning NXDOMAINs to the clients before even trying to hit the authoritative NS.
Re:Choosing a Public DNS Resolver by themacguffinman on Sunday June 28, 2026 @02:19AM (#48704892)
The downside is obviously that uncached queries take much longer (adding >100ms) and more queries are uncached since you can't share the cache with a large user-base. Unless you just visit the same websites over and over again, this results in worse overall performance.
Re:Choosing a Public DNS Resolver by kev009 on Sunday June 28, 2026 @05:34AM (#48705813)
I've never felt this. Most large services run or delegate to anycast DNS services.

If you have knowledge of TCP, you know you will occasionally get stalls much greater than that beyond control.

Re:Choosing a Public DNS Resolver by abcdefg12 on Sunday June 28, 2026 @05:11AM (#48705676)
Downside is privacy
Re:Choosing a Public DNS Resolver by kev009 on Sunday June 28, 2026 @05:37AM (#48705833)
Versus letting a singular entity snoop everything? If you actually open a connection to the result what is the difference? The only way to fully deal with all that is an overlay or mixnets.
Re:Choosing a Public DNS Resolver by abcdefg12 on Sunday June 28, 2026 @03:32PM (#48710713)
ISP snooping vs encrypted scatter to a bunch of dnscrypt resolvers