Cloudflare CNAME ordering issue?

Dave Lawrence tale at dd.org
Mon Jan 12 16:00:20 UTC 2026


https://www.cloudflarestatus.com/incidents/rk3dgkmy89kc

    "A recent software update inadvertently altered the ordering of
    DNS records within our cached responses. Specifically, the
    sequence of CNAME and non-CNAME records in the "answer" section
    was changed, which conflicted with the expectations of certain DNS
    client implementations. Upon identifying this behavior, we
    reverted the release to restore standard record ordering and
    resolve connectivity issues for affected users."

Anyone have some examples of what the answers looked like during the
incident?  I'm curious about how "the expectations of certain DNS
client implementations" were improper.  

>From another article I understood that that the Cisco problem was
they bombed out when they got the answer, but I'd not be inclined to
describe that quite as an issue of their expectations.


More information about the dns-operations mailing list