Re:Cloudflare 1.1.1.1 Incident on July 14, 2025
by Macha on Wednesday July 16, 2025 @06:16AM
(#44580577)
Cloudflare's own suggested config is to use their backup server 1.0.0.1 as the secondary DNS, which was also affected by this incident.
[ Parent
| on HN ]
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025
by stingraycharles on Wednesday July 16, 2025 @06:49AM
(#44580758)
TBH at this point the failure modes in which 1.1.1.1 would go down and 1.0.0.1 would not are not that many. At CloudFlare’s scale, it’s hardly believable a single of these DNS servers would go down, and it’s rather a large-scale system failure.
But I understand why Cloudflare can’t just say “use 8.8.8.8 as your backup”.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025
by bombcar on Wednesday July 16, 2025 @08:00AM
(#44581243)
At least some machines/routers do NOT have a primary and backup but instead randomly round-robin between them.
Which means that you’d be on cloudflare half the time and on google half the time which may not be what you wanted.
Re:Cloudflare 1.1.1.1 Incident on July 14, 2025
by toast0 on Wednesday July 16, 2025 @03:23PM
(#44585892)
It would depend on how Cloudflare set up their systems. From this and other outages, I think it's pretty clear that they've set up their systems as a single failure domain. But it would be possible for them to have setup for 1.1.1.1 and 1.0.0.1 to have separate failure domains --- separate infrastructure, at least some sites running one but not the other.