TL;DR

Cloudflare's 1.1.1.1 update altered the sequence of CNAME records, causing issues with DNS resolution. The post delves into the technical aspects and inconsistencies within DNS RFCs.

What happened

A recent change to Cloudflare's 1.1.1.1 service inadvertently changed the order of CNAME records in DNS responses, leading to resolution problems for some clients.

Why it matters for ops

Understanding the root cause and examining resolver code helps clarify ambiguities in DNS standards that can affect operational practices.

Action items

  • Review current DNS configurations for potential misordering issues
  • Update resolver software to handle ambiguous DNS RFCs better
  • Monitor DNS resolution errors closely post-updates

Source link

https://blog.cloudflare.com/cname-a-record-order-dns-standards/