GoKawiilCloudflare cuts DNS build memory 85% and halves propagation time
Cloudflare re-engineered its Zone Builder pipeline, which converts DNS record and zone setting changes into edge-ready data and writes them to Quicksilver. By adding a targeted build planner and a new scheduler that batches work per zone, the company avoided full rebuilds of zones with tens of millions of records whenever only a setting changed. This cut peak memory usage by 85% and, with the freed capacity, allowed the team to shorten built-in resilience delays, halving the time from a DNS change to its availability at the edge.
GoKawiil's interpretation of the reporting above, not reported fact.
As DNS zones grow toward hundreds of millions of records, naive full rebuilds on every change become increasingly expensive, so targeted partial builds could be necessary to keep propagation fast at scale. The engineering challenge was proving it was 'safe' to do a smaller build, since zone-level events can originate from multiple products and affect shared data across zones, meaning under-scoped builds risk serving stale or incorrect DNS answers. The freed-up memory headroom suggests Cloudflare could use similar techniques to further optimize latency or absorb future load growth.
- Cloudflare's Zone Builder now handles roughly 700 record changes and 100 other events per second, up from 250 in 2022.
- A new targeted build planner and scheduler avoid full rebuilds for zone setting changes, even on zones with 20+ million records.
- Peak memory usage dropped 85%, enabling a halving of the time from DNS change to data being written to Quicksilver.
Source: blog.cloudflare.com, 2026-11-02
Published there as: “We halved DNS build delay and cut memory use by 85%”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.