WHAT CAME FIRST: THE CNAME OR THE A RECORD?

Summary from the TLDR Dev newsletter

On January 8, Cloudflare's 1.1.1.1 DNS resolver had widespread resolution failures for users after a routine update accidentally reordered CNAME records in DNS responses. This subtle change broke some legacy DNS client implementations, such as glibc's `getaddrinfo` and certain Cisco switches, which incorrectly expected CNAME records to appear before other resource records.