What happened next: the deprecation of ANY
Blog post from Cloudflare
In April 2016, Cloudflare announced its plan to stop answering DNS "ANY" queries due to their lack of legitimate use, frequent malicious use, and involvement in large-scale DDoS attacks. The company proposed returning an error code to the querier, sparking a discussion within the DNS protocol community about whether ANY meant ALL. After various experiments and discussions, Cloudflare decided on an approach that returned harmless answers to ANY queries, reducing their amplification factor. This decision was aimed at making the internet a safer place by curbing large-scale DDoS attacks.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.