1min.

1MIN · GO

S2 made authoritative DNS a client of its account database

S2 replaced per-record managed DNS updates with a Go authoritative server that reads basin-to-cell mappings directly from its Spanner account database. This avoids a separate update queue when customers create namespaces. Cloudflare DNS Firewall protects the origin, while replicas run in two regions. The design trades synchronization delays for database dependencies and responsibility for operating DNS.

S2 · Nov 16, 2026

Why it matters

A control-plane limit can force architectural change even when the managed service’s ordinary query path works well.

More context

The team used miekg/dns, checked RFC behavior with Ferret and retained a separate Route53 zone for certificate challenges. The origin accepts Cloudflare traffic only, with tests checking that responses do not expose origin nameserver addresses. Read the failure modes before copying the pattern.

Keep in mind

Author-reported production design. The cited Route53 write limit describes their earlier experience; the article notes current limits may differ. Caching, DNSSEC and unseen failure modes remain work in progress. Running DNS adds costs, alerts and recovery procedures.

Original read

More engineering ideas, one minute at a time.

Explore more stories