This will be a rollercoaster story on how we ended up replacing Route53 and running our own authoritative DNS server.

At some point, we decided we should be able to provide unlimited basins to our clients. Basins are a core namespace construct on S2 and act as top-level containers for streams (already unlimited in number). We found that customers were hacking around our not-so-arbitrary limit of 100 basins per account. That’s not a cool experience.

For the purposes of this story, what is important is that each basin created by a customer becomes its own subdomain: my-basin.b.s2.dev (not different from the way buckets work on AWS S3). The DNS entry associated with each basin is a CNAME, which routes clients to the correct cell in our architecture. To support unlimited basins, we'd therefore need to support unlimited DNS records.