It’s always DNS, so why are we running our own?
Summary
An engineering case study of moving from AWS Route53 to a custom authoritative DNS server to support unlimited basins and instant DNS resolution. It covers the limitations of third-party DNS APIs, the rationale for building a bespoke DNS service, and the tech stack (Go, miekg/dns, Google Cloud Spanner) used to serve records. It also discusses security hardening with Cloudflare DNS Firewall, DNS delegation, and HA architecture, plus ongoing challenges like NXDOMAIN-based DDoS and forthcoming DNSSEC work.