It’s always DNS, so why are we running our own?
Not investment advice. Muhabbit scores how much a story may matter, not which way to trade.
S2 replaced AWS Route53 with its own authoritative DNS server after Route53's roughly 5 UPSERTs-per-second API limit caused a backlog when a single actor rapidly created tens of thousands of basins, forcing the company to cap accounts at 100 basins. Each basin is a CNAME subdomain (e.g., my-basin.b.s2.dev) that must resolve instantly, so unlimited basins required unlimited, strongly consistent DNS records. S2 found similar API throttling at GCP Cloud DNS, Cloudflare and Azure DNS, ruling out managed providers and prompting it to build a custom system that queries an up-to-date zone map on every request. The move matters because DNS update throughput had become a hard constraint on S2's core namespace product, and the incident-driven 100-basin cap was a workaround rather than a fix. Watch whether the in-house server delivers instant consistency at scale and whether S2 lifts the account limit.
Muhabbit's AI wrote this summary in its own words from Hacker News's report. It can get details wrong, so check the source.
Named in this story
AWS Route53, S2