An update to cache implementation in Cloudflare’s DNS resolver led to DNS resolution failures due to CNAME and A record ordering issues.
DNS clients differ in how they handle the ordering of CNAME and A records in the responses: some expect the CNAME record to be before the A record, while others do not require any specific order. Cloudflare states that their interpretation of the RFC 1034 did not mandate any specific order, leading to the issues when some clients expected CNAME before A record.
They also mention that even if the RFC is interpreted to have CNAMEs before A record, the resolution might still fail if multiple CNAME records are not in the expected order. For …