ZeroDailyGet it on Google Play

We ditched Amazon Route53 and rolled our own DNS server. Here's why.

Original headline: It's always DNS, so why are we running our own? — s2.dev

More in Programming and developer news

When building their S2 platform, the team needed to support unlimited 'basins' (top-level containers), each requiring its own DNS record with strong consistency for instant availability. They initially used AWS Route53, but discovered a critical limitation: API rate limits of about 5 UPSERTs per second. These limits were painfully exposed when a malicious actor rapidly created tens of thousands of basins, saturating the quota and causing a multi-hour backlog that blocked normal DNS updates.

The incident forced them to enforce an arbitrary 100-basin limit—a poor user experience. Their requirement for unlimited, instantly-available DNS records couldn't be met by any major managed provider (Route53, Cloudflare, GCP, Azure), all of which have similar API constraints. This led to the daunting but necessary decision to build and run their own authoritative DNS server, trading managed convenience for the control and scale their product demanded.

Read the original at s2.dev

Satirical commentary on real tech news, summarised with AI. Read the original source for the facts. How ZeroDaily works

Open in the appGet it on Google Play

More stories

Add ZeroDaily on Google