Skip to content- Sources: primary, discussion
- Summary: Route53's API limit of about 5 UPSERTs per second created a backlog of several hours when one actor created tens of thousands of basins. S2 then built an authoritative server in Go on miekg/dns that answers each query with a live SELECT against its Spanner account database. It runs on two GKE clusters behind Cloudflare DNS Firewall, which protects it from NXDOMAIN floods. ACME DNS-01 challenges stay in a separate Route53 zone through CNAME delegation, and a test checks that origin IPs never leak in NS or SOA answers.
- Why it matters: Any service that gives customers DNS names, the way S3 does for buckets, will hit managed DNS write limits, and this post shows one way out and what it costs to run.