DNS / Global Traffic Management
4SO GeoDNS
Authoritative DNS and traffic management with an API-first control plane, revisions, DNSSEC and a serving path independent of the manager.
- Authoritative DNS
- DNSSEC
- Revisioned delivery
- Geo policy
- Node lifecycle
The problem
Problem
DNS must keep serving during control-plane impairment while zone, policy and DNSSEC changes still need consistency and explicit rollback.
Why It Is Hard
Serving availability, configuration distribution, revision history and node lifecycle must stay coordinated without unnecessary coupling.
The decision
Leadership / Architecture Role
Designed control/data-plane separation, immutable revisions, safer rollout and evidence-backed node lifecycle.
Key Decisions
Keep the manager out of the serving path, make configuration revisioned and turn node onboarding into a durable workflow with trust bootstrap.
The architecture
Architecture
The manager owns desired state and revisions; DNS nodes keep serving independently; rollout is driven by validated artifacts and health readback.
Failure & Recovery Model
Control-plane failure must not stop existing serving; incomplete rollout must be observable and the previous revision must provide a clear recovery path.
Security / Authority Model
DNSSEC, trust bootstrap, least privilege and audit trails are part of the lifecycle; raw secrets and private topology are not exposed on public surfaces.
The value
Product Experience
Operators see zones, policies, rollout and node health as understandable workflows rather than a collection of manual SSH steps.
Value Created
DNS moves from sensitive manual operations to a revisioned, auditable and recoverable service capability.
The boundaries
Trade-offs
To preserve availability, serving state remains separate from management state; reconciliation therefore needs to be explicit and observable.
What Was Intentionally Excluded
Putting the manager in the query path, hidden authoritative state or changes outside the revision workflow are intentionally excluded.
Truth boundary
Current Truth / Limitations
Serving state is not inferred from manager state; data-plane health and rollout evidence remain independently observable.
designed → source implemented → runtime tested → production certified
Each level is claimed separately; a lower level never implies a higher one.
Start a conversation
If technology should move your organization forward rather than hold it back, let’s talk.
The first conversation is about your problem, not about me: where you are stuck, what is at stake and whether I am the right person to solve it.
Bring the problem