DNS Reliability Issues

The cluster focuses on concerns about DNS as a single point of failure, criticism of centralized providers like Cloudflare, and discussions on improving resilience through decentralization, redundancy, and proper TTL management.

📉 Falling 0.5x DevOps & Infrastructure
5,625
Comments
20
Years Active
5
Top Authors
#3426
Topic ID

Activity Over Time

2007
3
2008
52
2009
124
2010
187
2011
180
2012
303
2013
264
2014
322
2015
211
2016
442
2017
276
2018
315
2019
384
2020
414
2021
667
2022
390
2023
391
2024
321
2025
350
2026
29

Keywords

R720 OK AWS ICANN SRV TTL GB UDP CEO DNS dns servers cloudflare server authoritative provider single point failure point failure single point caching

Sample Comments

fredski42 Jul 22, 2021 View on HN

I thought DNS was supposed to be resilient

olliej Dec 10, 2020 View on HN

Someone has to run the DNS servers the browsers talk to - DNS data is big and can change rapidly, especially in the cloudflare and AWS type of cases

chrisjsmith Jul 5, 2011 View on HN

Centralised DNS = bad. That's the issue.

davidjgraph Jul 22, 2021 View on HN

Serious question, has anyone properly solved the issue of DNS as a single point of failure?

r1ch Oct 21, 2016 View on HN

Surprised to see so many big names relying on a single provider. DNS is designed to be distributed, it should be possible to avoid a single point of failure.

ibcnu2 Jun 18, 2013 View on HN

Wouldn't simply owning the DNS be more efficient?

sharts Apr 17, 2024 View on HN

Perhaps using something like a split-horizon DNS setup would alleviate that

1MachineElf Sep 17, 2021 View on HN

At least you've removed one single point of failure for DNS lookups.

DDoS'ing DNS providers is common enough...

cube00 Nov 19, 2014 View on HN

Wouldn't that kill DNS if everyone did that considering it relies on caching for performance across the world?