Remix.run Logo
▲ misker1 21 minutes ago

Ah, I wrote strong consistency but what I really meant was atomic, on the creation side. Before, our basin DNS entries were created async in Route53, and they could stay in that Creating status for a long time (DDoS, provider limits, etc.). Now, once the API says 200, the DNS entry is guaranteed to exist at our nameservers.

Clients use regular resolvers, no special server, accessed via http2. The funny thing is that we actually had a client who was relying on DNS being strongly consistent. Since that isn't really feasible, we asked them to add a small delay after creating a basin, and they did.