Dyn issues affecting joint customers

What this post added

This post describes a specific incident where an external DNS attack on Dyn affected joint Cloudflare and Dyn customers. It details the mechanism of failure (CNAME records pointing to Dyn causing DNS query failures) and the resulting error (1001). Workarounds are provided: switching to A/AAAA records or migrating to Cloudflare as the authoritative DNS provider. It also highlights the potential impact on Cloudflare's own status page and support system due to third-party hosting.