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.
[ Parent
| on HN ]
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.