Re:Cloudflare 1.1.1.1 Incident on July 14, 2025
by jeffbee on Wednesday July 16, 2025 @11:25AM
(#44583314)
You know, I recently went through a period of thinking my MacBook was just broken. It had the janks. Everything on the browser was just slower than you're used to. After a week or two of pulling my hair, I figured it out. The newly-configured computer was using the DHCP-assigned DNS instead of Google DNS. Switched it, and it made a massive difference.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025
by dylan604 on Wednesday July 16, 2025 @11:55AM
(#44583690)
but that's the opposite of the request to move from a googDNS to a local one because of latency. so your ISP's DNS sucked, which is a broad statement, and is part of the why services like 1.1.1.1 or 8.8.8.8 exist. you didn't make the change of DNS because you were picking one based on nearest location.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025
by jeffbee on Wednesday July 16, 2025 @12:04PM
(#44583827)
There is more to latency than distance. Server response time is also important. In my case, the problem was that the DNS forwarder in the local wifi access point/router was very slow, even though the ICMP latency from my laptop to that device is obviously low.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025
by dylan604 on Wednesday July 16, 2025 @02:41PM
(#44585517)
which is well and fine, but my original comment was that moving to a closer DNS isn't worth it just for being closer especially when it is usually your ISP's server. so now, you're confirming that just moving closer isn't the solve, so it just reassures that not using the closest DNS is just fine.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025
by tredre3 on Wednesday July 16, 2025 @12:45PM
(#44584347)
news.ycombinator.com has a TTL of 1, so every page load will do one DNS request (possibly multiple).
If you choose a resolver that is very far, 100ms longer page loads do end add up quickly...
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025
by sumtechguy on Wednesday July 16, 2025 @03:05PM
(#44585733)
Even something simple like www.google.com serves from 5 different DNS names. I have seen as high as 50. It is surprisingly snappier. Especially on older browsers that would only have 2 connections at a time open. It adds up faster than you would intuitively think. I used to have local resolvers that would mess with the TTL. But that was more trouble than it was worth. But it also gave a decent speedup. Was it 'worth' doing. Well it was kinda fun to mess with, I guess.
I get that in theory blah blah, but we now have choices in who gets to see all of our requests and the ISP will always lose out to the other losers in the list