Re:Cloudflare 1.1.1.1 Incident on July 14, 2025
by immibis on Wednesday July 16, 2025 @07:07AM
(#44580866)
HN users might prefer to run their own. It's a low maintenance service. It's not like running a mail server.
[ Parent
| on HN ]
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025
by daneel_w on Wednesday July 16, 2025 @08:19AM
(#44581406)
I think that might be overestimating the technical prowess of HN readers on the whole. Sure, it doesn't require wizardry to set up e.g. Unbound as a catch-all DoT forwarder, but it's not the click'n'play most people require. It should be compared to just changing the system resolvers to dns0, Quad9 etc.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025
by lossolo on Wednesday July 16, 2025 @11:24AM
(#44583310)
One issue here is that you can be tracked easily.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025
by kachapopopow on Wednesday July 16, 2025 @05:43PM
(#44587120)
Running your own and being the sole user is the exact same thing as using a dns server (you need to obtain nameservers for any given domain which you have to contact a dns server for).
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025
by BenjiWiebe on Thursday July 17, 2025 @11:52AM
(#44594701)
Except that your queries are spread out to different places instead of all being sent to a single server.
You ask .com resolver for domain.com's NS, and then you ask ns1.domain.com for foo.domain.com. Then you browse to wikipedia.org, and none of those DNS queries go to the same place as the previous site.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025
by kachapopopow on Friday July 18, 2025 @12:02AM
(#44601082)
That's arguably worse since you are now in direct contact with the nameservers (which are usually managed by non privacy orientated providers).