What came first- the CNAME or the A record
A recent change to 1.1.1.1 accidentally altered the order of CNAME records in DNS responses, breaking resolution for some clients. This post explores the technical root cause, examines the source code of affected resolvers, and dives into the inherent ambiguities of the DNS RFCs.
Discussion around the web
- Hacker News466 · 162 💬
Score breakdown
- Technical depth96
- Practical value45
- Originality85
- Writing quality82
- Source reputation90
- Recency0
- External engagement37
- On-site engagement0
More like this
Slack Engineering57
The Case of the Recursive Resolvers
unknown·17 min read
Stripe Engineering61
The secret life of DNS packets: investigating complex networks
unknown·14 min read
The GitHub Blog34
Git.io no longer accepts new URLs - GitHub Changelog
Person·unknown·2 min read
The Cloudflare Blog59
1.1.1.1 lookup failures on October 4, 2023
unknown·17 min read
Engradar shows a summary and links to the original article. The full article is hosted on blog.cloudflare.com.