Documentation
Operator guides for running DNS Fabric in production.
Learn the control plane model, connect providers, and understand how DNS Fabric verifies, reconciles, and audits changes across your DNS estate.
Orientation
Explain the system model before anyone clicks a button.
The strongest public docs are clear, hierarchical, and operational. This section leads with system truth, operator flow, and the next actions a serious customer actually wants.
Authoritative provider reads
DNS providers remain the source of truth. Metadata and cache support operations but never overwrite live state.
Verification first
Every control action follows observe, compare, decide, and only then reconcile when drift is confirmed.
Operator-centric workflows
Documentation focuses on setup, visibility, auditability, and predictable change handling.
Operator flow
$ dnsfabric verify provider cloudflare
observe -> fetch live zone + records from provider
compare -> normalize records and compute deterministic hash
decide -> detect drift, health, and reconciliation priority
reconcile -> update secondaries only after drift is confirmed
record -> refresh Redis cache and write audit / health state