Dyn issues affecting joint customers
Oct 21, 2016Filippo Valsorda

Summary
This post addresses an ongoing large-scale Denial-of-Service attack against Dyn DNS, which may affect joint Cloudflare and Dyn customers. It explains that CNAME records pointing to Dyn-hosted zones can cause website unavailability (1001 error) due to failed DNS queries to Dyn. Workarounds include updating Cloudflare DNS records from CNAMEs to A/AAAA records pointing directly to the origin IP, or migrating the authoritative DNS hosting to Cloudflare. The post also notes that Cloudflare's status page and support system might be affected due to their reliance on third-party hosting.
More from the DNS Infrastructure & Naming Conventions trail
- The keys to the Internet change on October 11, 2026. Are you ready?
- 1.1.1.1 now supports post-quantum DNSSEC, all 2,420 bytes of it
- How we saved 100 terabytes of memory by optimizing 1.1.1.1’s DNS cache
- BGP ORIGIN attribute manipulation and its impact on the Internet
- Cloudflare Internal DNS is now generally available