1. 4SO
  2. Products
  3. GeoDNS

Authoritative DNS and global traffic

4SO GeoDNS

A DNS control plane with an independent serving path.

API-first management of DNS desired state, validation, immutable revisions, blue/green delivery, health-aware routing, DNSSEC and node lifecycle in a single process, while the query path remains independent of the Manager.

  • Authoritative DNS
  • Global Traffic
  • DNSSEC
  • Blue / Green
4SO GeoDNS flow: Observe traffic, Understand topology, Resolve by policy, Monitor health, Optimize decisions.
Who it is for
Organizations and providers that run authoritative DNS for their domains across regions and under real traffic.
What it does
Versions and validates every zone change, ships it to nodes through blue/green delivery, and runs DNSSEC, TSIG and geo- and health-aware routing.
Where it runs
A Manager and DNS nodes in your own environment. Each node answers from verified local state, so serving continues when the Manager is unavailable.
ZONE REVISION · BLUE / GREENPublishing a DNS change without touching the active answer path
01

DNS answers come from the active color and do not depend on the manager.

01Problem

A small DNS change can have a large blast radius.

Authoritative DNS must be fast and always available, while its changes must be precise, auditable and reversible. GeoDNS separates the configuration path from the serving path.

  1. 01

    Serving must not depend on the Manager

    The query path stays on the DNS node and its last verified state.

  2. 02

    No direct changes to the runtime

    Records and policies first become a revision, then are staged and verified.

  3. 03

    Traffic policy needs trustworthy data

    Endpoint health and eligibility come from accepted observations, not from simulated browser state.

  4. 04

    DNSSEC has its own lifecycle

    Keys, signing, rollover and recovery must be as controlled as zone management.

02Capabilities

Zones, traffic and security in one control plane.

Beyond authoritative records, GeoDNS treats delivery, traffic management and node lifecycle as part of the same product.

  1. 01

    Type-safe zones and records

    Forward/reverse zones, typed RRsets and controlled import/export.

  2. 02

    Immutable Revisions

    Changesets, snapshot hashes and revisions for audit and rollback.

  3. 03

    Blue/Green Delivery

    Stage on the inactive color, read back state, then cut over atomically.

  4. 04

    Global Traffic Management

    Endpoints, pools, regions, health perspectives and answer policy.

  5. 05

    DNSSEC lifecycle

    Signing, DS evidence, rollover and restore/reconcile.

  6. 06

    Secondary / Transfer

    TSIG, AXFR/IXFR, catalog zones and secondary provider lifecycle.

  7. 07

    DNS node operations

    Onboard, drain, replace, remove and fleet rollout.

  8. 08

    DNS Observability

    Health, metrics, alerts, incidents and synthetic DNS probes.

4SO

The normal query path stays short: Resolver → DNS node → active runtime → local state. No regular query depends on the Manager or a cross-region database to be answered.

03Deployment model

From one Manager and one DNS node to multiple regions.

The minimum product topology is simple, and HA or multi-region is not a prerequisite; nodes and regions are added incrementally.

ProfileControl PlaneServing PlaneUse case
Basic1 Manager1 DNS nodeSimple, complete authoritative DNS setup
Multi-nodeCentral ManagerMultiple DNS nodesServing redundancy and controlled rollout
Multiple sitesSingle control planeNodes across multiple sitesFailure-domain separation and proximity to resolvers
Multi-regionCentral management with regional processesIndependent serving in multiple regionsGlobal traffic and broad resilience
04Lifecycle

Every DNS change has an observable path.

Going from edit to publish is more than a few clicks; validation, revision, stage, state read-back and recovery each have a defined state.

  1. 01EditEdit
  2. 02ValidationValidate
  3. 03Build revisionSeal
  4. 04StagingStage
  5. 05State read-backVerify
  6. 06PublishCutover
  7. 07MonitoringObserve
05Profiles

Authoritative DNS is more than a zone editor.

Every layer, from authoritative data to global traffic and security, has its own operational profile.

  • Authoritative DNS

    Zone and RRset management with revisions.

    • Forward / Reverse
    • Typed RRsets
    • Scheduled / templated changes
  • Traffic Management

    Answers based on endpoint and policy.

    • Pools / Endpoints
    • Geo / health policy
    • Maintenance windows
  • DNS Security

    Trust and transfer security inside the product.

    • DNSSEC signing / rollover
    • TSIG
    • Transfer policy
  • DNS node fleet

    Lifecycle of serving nodes.

    • Enroll / mTLS
    • Drain / Replace
    • Fleet rollout
  • Delivery

    Safe, reversible publishing.

    • Inactive staging
    • State read-back validation
    • Atomic cutover
  • Recovery

    Protecting management state.

    • Backup / Restore
    • Release rollback
    • Disaster recovery process
Technical reference

Architecture, workflows and operations in detail

For engineers who want to know how the product works underneath: components, boundaries, failure behavior and the operations it runs.

06Architecture

The configuration path is longer; the serving path is deliberately short.

A DNS change must pass through validation, revision and delivery. DNS answers, however, are served directly from the node's verified runtime.

  1. CONTROL
    Panel / Product APIAuthentication, domains, RBAC and typed validation.
  2. AUTHORITY
    Desired state / Revision / JobTransactional state, immutable revisions, audit and evidence.
  3. DELIVERY
    Worker + Node Agent over mTLSStage, state read-back, verify and atomic cutover.
  4. SERVING
    Authoritative DNS nodednsdist and the active PowerDNS runtime with verified local state.
LayerComponentResponsibilityFail-safe behavior
Product APIFastAPI + scoped RBACZone/RRset, traffic policy, node lifecycle and typed validationThe browser never mutates the DNS runtime directly
AuthorityPostgreSQL + transactional outboxDesired state, audit, job/revision stateMutation and event publication within one transactional boundary
DeliveryWorker + mTLS Node AgentStage inactive color, read-back, verify and atomic cutoverFailed delivery stops before serving
DNS EdgednsdistStable serving entry and selection of the active PowerDNS colorThe query path does not depend on the Manager
Authoritative RuntimePowerDNS blue/green + local PostgreSQLServes the last verified revisionA control-plane outage keeps DNS answering from the last healthy state
SecurityDNSSEC · TSIG · transfer policySigning, rollover and zone-transfer trustSecret material never enters Panel/Audit/Evidence
TECH

Geo-routing & Health Contract. DNS decisions are read from the compiled policy and a local snapshot; the query path never runs a network health check at answer time.

DomainInput / MechanismTechnical contract
Client localityECS or Recursive Resolver IPValid ECS is used when permitted; otherwise the resolver IP is the basis for selection.
Geo / network matchCIDR, ASN/Organization, Country/Subdivision/Continent/CityPrecise overrides and geography are evaluated by numeric priority in deterministic order.
Native GeoIPPowerDNS geoip backend + Country/ASN MMDBGeoIP sits alongside gpgsql; zone data is not moved from the primary authority into a YAML/GeoIP backend.
HealthTCP/UDP/HTTP/HTTPS/TLS/DNS/gRPC/ICMP probesHealth is computed outside the query path, and states such as HEALTHY/DEGRADED/SUSPECT/UNHEALTHY are recorded in a versioned snapshot.
Policy compilerStructured policy → trusted runtime materialArbitrary Lua is not accepted; the compiler produces reproducible output with a hash bound to the revision.
SimulationResolver/ECS/time/health/dataset inputsRule match, selected pool/endpoint, fallback path, answer and TTL can be simulated before publish.
ECS cache isolationPolicy-aware cache keyingAnswers that depend on the client network must not leak through the cache across unrelated ECS contexts.
07Workflows and failure

A job is retried only when its effect on the system is known.

Mutations are idempotent and project-scoped; node mutation, fleet rollout and certificate rotation never stay open concurrently on the same node. Worker ownership is fenced with a lease and an execution epoch.

  1. 01QueueQUEUED
  2. 02LeaseRUNNING + EPOCH
  3. 03StageVERIFY / CUTOVER
  4. 04SuccessSUCCEEDED
BLUE / GREEN CUTOVER

Stage on the inactive color

DNS read-back happens before the active color is switched.

DNS QUERY ENTRY
↓
ACTIVE
BLUE
⇄
STAGED
GREEN
↓
DNS
VERIFY
revision → stage inactive → authoritative read-back → atomic cutover
A failed stage does not change active serving.
HEALTH BRANCH

Primary or fallback based on the snapshot

The query path never runs a network probe at request time.

CLIENT CONTEXT
ECS / RESOLVER
↓
POLICY + HEALTH SNAPSHOT
↓
PRIMARY
HEALTHY?
PRIMARY
↙ ↘
FALLBACK
Health state is versioned; a stale snapshot can block policy.
DR LOOP

Readiness → Failover → Failback

DR actions are bound to the readiness hash and topology freeze.

PRIMARY
SITE
→
READINESS
GATE
↓
FENCE
+ HASH
↑
DR
SITE
←
FAILBACK
VERIFY
backup ready → approval → failover → serving verify → controlled failback
Stale readiness or unknown external state goes to reconcile.
  1. Flow 01

    Publish Zone Revision

    The change is staged on the inactive color first.

    1. Validate
    2. Build Revision
    3. Compile Policy
    4. Stage Inactive
    5. DNS Read-back
    6. Atomic Cutover

    Failure and recoveryA failed stage does not change the active query path.

  2. Flow 02

    Traffic Policy

    Geo/network policy is simulated before publish.

    1. Policy Input
    2. Priority Order
    3. ECS / Resolver Context
    4. Simulate
    5. Compile
    6. Publish

    Failure and recoveryArbitrary Lua and priority conflicts are rejected before serving.

  3. Flow 03

    Node Onboarding

    A node joins the fleet only after trust and serving verification.

    1. Identity / mTLS
    2. Preflight
    3. Bootstrap
    4. Register
    5. Health
    6. Rollout Eligible

    Failure and recoveryBootstrap failure does not turn into a blind retry.

  4. Flow 04

    DNSSEC Rotation

    Key lifecycle runs with overlap and serving acknowledgement.

    1. Key Intent
    2. Generate / Import
    3. Stage
    4. Overlap
    5. Observe Signing
    6. Retire Old

    Failure and recoverySecret material never enters public Panel/Audit/Evidence.

  5. Flow 05

    Restore / DR

    Restore and site failover are bound to readiness evidence.

    1. Backup Ready
    2. Preflight
    3. Approval
    4. Restore / Failover
    5. Serving Verify
    6. Commit / Failback

    Failure and recoveryUnknown external state → RECONCILE_REQUIRED, not blind replay.

Additional operational flows

Health and node replacement directly affect serving quality and need their own flows.

  1. Flow 06

    Health Snapshot → Routing

    Health is collected outside the query hot path and turned into a versioned snapshot.

    1. Probe Policy
    2. Schedule
    3. Out-of-band Probe
    4. Publish Snapshot
    5. Compile Traffic Policy
    6. Node Sync
    7. DNS Verify

    Failure and recoveryStale or unknown health is never automatically assumed healthy and must not shift traffic without cause.

  2. Flow 07

    Drain / Replace DNS Node

    The old node leaves only after the replacement is ready and serving is verified.

    1. Fleet Intent
    2. Serving Capacity
    3. Stop Eligibility
    4. Bootstrap Replacement
    5. Stage Active Revision
    6. Serving Read-back
    7. Remove Old Node

    Failure and recoveryUntil the replacement returns correct authoritative answers, removal of the old node does not reach its final step.

Action / FlowAdmission / PreconditionsExecution / LockSuccess CriterionFailure / Recovery
Publish Zone / RRsetTyped validation, revision and policy compile before deliveryStage on inactive color → node read-back → atomic cutoverAuthoritative answer/TTL and active revision confirmed from the serving pathA failed stage does not change serving; rollback to the preserved healthy color
Traffic PolicyStructured policy, priority and simulation without conflictCompiler material is versioned; health snapshot is consumed outside the query pathMatched rule/pool/endpoint and synthetic DNS behavior match the revisionArbitrary Lua is rejected; policy conflict fails before publish
Node Onboarding / ReplaceIdentity/mTLS, preflight and node mutation availabilityDurable job with node lock; onboarding/day-2/fleet/cert-rotation overlap is rejectedNode observed healthy and rollout eligibility clearNode onboarding failure does not become a generic retry; a fresh bootstrap may be required
DNSSEC / CertificateKey/identity lifecycle and approval for sensitive operationsStage/overlap/ack and owner-specific rotation workflowSigning/serving or certificate observation matches the expected generationStale rotation/concurrent fleet mutation rejected; secret material removed from the public job projection
Control-plane RestoreBackup must be READY, repository-verified and carry snapshot/hash evidencePreflight → approval → execution → cutoverRESTORED only after preflight binding and runtime verificationWorker interruption/unknown external state → RECONCILE_REQUIRED; blind retry prohibited
DR Failover / FailbackReadiness job, topology freeze, fencing, rollback and RPO acknowledgement requiredThe action is bound to readiness state/hash and profile revisionActive site/traffic/database state reaches the expected phaseStale readiness or topology mismatch rejected; failback allowed only from FAILED_OVER
FLOW

Retry classification is explicit to the operator: SAFE_TO_RETRY, RECONCILE_REQUIRED, FRESH_BOOTSTRAP_REQUIRED or FRESH_HEALTH_REQUEST_REQUIRED. Lease loss in disruptive workflows is never permission for blind replay.

08Operations catalog

DNS operations are controlled in proportion to their blast radius.

Operators use the same product process and audit trail to change records, roll out nodes or manage DNSSEC.

  • Create / Edit ZoneZone and RRset management with validation and revisions.
  • PublishStage, state read-back and atomic cutover to the new version.
  • RollbackReturn to the preserved healthy color.
  • Traffic PolicyManage endpoints, pools and health-aware response policy.
  • DNSSECSigning, rollover and restore/reconcile.
  • Node onboardingEnroll and prepare DNS nodes with controlled identity.
  • Drain / ReplaceRetire or replace nodes without directly changing the zone runtime.
  • ObserveHealth, metrics, alerts and synthetic DNS behavior.

Run DNS with serving speed and the rigor of a distributed system.

4SO GeoDNS controls changes without putting the Control Plane in the DNS answer path.