If you're running a k8s cluster, you're already running a DNS server. It shouldn't be too scary IMO, but I've also wasted a lot of time writing DNS-related libraries and application in the past, so I'm probably biased.<p>I find the following part of the article interesting.<p><pre><code> These [DNS] records would need strong consistency too. When a basin is created, its address should be instantly resolvable, otherwise clients would be waiting around for a cached NXDOMAIN to expire.
</code></pre>
DNS is, almost by design, an eventually consistent system. Strong consistency would mean authoritative servers for a zone have to coordinate updates and agree on the current state before answering queries. That would almost defeat the availability goals that date back to the very origin of DNS. To quote the very old RFC 1034:<p><pre><code> Access to information is more critical than instantaneous updates or guarantees of consistency
</code></pre>
I am guessing S2 has clients query a specific DNS server directly so that there is strong consistency in practice. Also, it's unclear to me whether it's intended for records to propagate to other name servers. It'd be nice if the article included an appendix for people who don't know what S2 is (or how clients typically access the service).
> DNS is, almost by design, an eventually consistent system.<p>I agree with this. Offering instant updates creates a large performance benchmark, especially if you experience massive growth. Unless this is mitigated with TTL to some extent? I would personally be looking at how to reduce the database load for misbehaving clients e.g. 5 second cache on all queries or allowing a customer to choose a "tier" where they won't need fast instant updates. If they choose e.g. 5 minutes TTL, you can cache these extensively, even just as disk files rather than RAM.