Nervous ISPs replace Chrome as strange consumers of DNS resources

ICANN reports that Chrome’s share of DNS root-server traffic fell from 45% to 1% after Google fixed the flaw that drove excessive queries. It has identified some ISPs sending each DNS request to three resolvers and repeating many non-cached requests, but says those ISPs do not appear to be major players; ICANN is researching the cause and warns wider adoption could strain DNS infrastructure. The number of resolver farms visible to half of internet users has declined from nearly 250 in 2020 to just under 150 today, which ICANN suspects may reflect increasing provider concentration.

Analysis

Low near-term earnings signal; a resilience and concentration watch. The notable market mechanism is not raw DNS query growth but duplicated, potentially unpaid resolver workload. If this behavior spreads, Google and Cloudflare could absorb more infrastructure load without a corresponding increase in monetizable demand; there is no evidence here that the observed ISPs are large enough to move either company’s costs or reported results. Treat the traffic data as an operational warning, not a revenue catalyst.

Over 1–3 months, the key catalyst is whether ICANN identifies the ISPs or establishes that the practice is becoming more common. A broader rollout could prompt resolver operators to invest in capacity and could increase scrutiny of reliance on a smaller set of large providers. Over 6–18 months, further concentration could raise systemic resilience and competitive concerns, but it does not by itself establish regulatory action or durable pricing power for Google or Cloudflare.

Contrarian point: more traffic to large resolvers is not necessarily beneficial to them. If it is redundant, unpaid demand, it is load rather than customer adoption. Conversely, resilience concerns could support demand for independent DNS operators, but the article provides no evidence yet of switching or willingness to pay. No fundamental trade is justified on this signal alone.

Key Decisions for Investors

• No immediate position in GOOG or NET based solely on this report; the observed behavior appears too small and its unit economics are unknown.
• Put DNS query volumes, infrastructure-cost commentary, and any guidance on network investment at Google and Cloudflare on the watchlist. Reassess if either company indicates material, persistent cost growth tied to resolver traffic.
• Use ICANN’s follow-up as a 1–3 month catalyst check: verify which ISPs are involved, whether the behavior is expanding, and whether duplicated requests are materially reaching resolver operators rather than being absorbed or filtered upstream.
• Falsify the low-impact view if ICANN documents adoption by major ISPs or a sustained increase in redundant traffic, or if GOOG/NET disclose a material cost or service-quality impact; absent such evidence, avoid treating DNS concentration as a near-term earnings catalyst.