We halved DNS build delay and cut memory use by 85%

Cloudflare’s authoritative DNS infrastructure must turn customer zone changes into data that can be served across its network. The previous build process did more work than necessary: a change affecting a zone could trigger broad processing, consuming memory and delaying the point at which updated DNS records became available. The redesign makes builds targeted, so the system focuses on the zone that changed rather than repeatedly handling unrelated zone data. Kafka carries the change events, while Quicksilver is part of the distribution path that makes the resulting data available across Cloudflare’s network.

The shift reduced DNS build delay by half and cut memory use by 85%. These gains matter because DNS updates are time-sensitive, while the system must handle changes across a very large number of zones without exhausting resources. Targeting the build work improves both propagation speed and efficiency: less unnecessary data is processed, reducing resource pressure and helping updates move through the pipeline faster. The account is chiefly about an infrastructure redesign and its measurable operational results, rather than changes to DNS behavior or a new customer-facing feature.