I am very petty about this one bug and have a very old axe to grind that this reminded me of!

I am very petty about this one bug and have a very old axe to grind that this reminded me of! Way back in 2011 CloudFlare launched an incredibly poorly researched feature to just return CNAME records at a domain apex ... RFCs be damned. https://blog.cloudflare.com/zone-apex-naked-domain-root-doma... , and I quote directly ... "Never one to let a RFC stand in the way of a solution to a real problem, we're happy to announce that CloudFlare allows you to set your zone apex to a CNAME." The problem? CNAMEs are name level aliases, not record level, so this "feature" would break the caching of NS, MX, and SOA records that exist at domain apexes. Many of us warned them at the time that this would result in a non-deterministic issue. At EC2 and Route 53 we weren't supporting this just to be mean! If a user's DNS resolver got an MX query before an A query, things might work ... but the other way around, they might not. An absolute nightmare to deal with. But move fast and break things, so hey :) In earnest though ... it's great to see how now CloudFare are handling CNAME chains and A record ordering issues in this kind of detail. I never would have thought of this implicit contract they've discovered, and it makes sense!

Posted by colmmacc on Jan 20, 2026, 1:12 AM

Tags

• hackernews (Network)

Related issues

• (1) Because it doesn't actually solve the problem.
• Every time fossil comes up, I hear this same issue - "why is there no rebase?" And honestly, I've never been able to get this argument.
• My biggest problem with running local LLMs on my M4 Max/128GB RAM is the prefill latency.
• Biggest problem with httpx I see is authors sanity https://github.com/encode/httpx/discussions/3784 .
• There aren't many situations today that make one think: Why doesn't this business have a website?
• > IAM can stay MS That's leaving the most critical component still with a US company.