3 articles
The technical companion: five components, two namespaces (public vs. internal split-horizon), one writer, two nameservers in two locations. Architecture, configuration samples, measured change latency, security, and how we verified the cutover.
This week, frao.tech began to be served by nameservers we own and operate ourselves — two independent hosts, two locations, one platform we control end to end. What the milestone means, what it gives us, and what it asks of us.
On 2026-07-31, a global out-of-memory cascade froze the primary host twice. Root cause: a fallback price with no authority signal, a risk engine with no dedupe, and a container with no memory ceiling. A case study in how complex systems fail at the seams.