ZelnickSignal hub
UTC --:--

Infrastructure product / In the lab

OrbitDNS

A macOS DNS control surface turning provider-heavy operations into guided, inspectable workflows.

ACTIVE SIGNALPROVIDER COMPLEXITY, MADE LEGIBLE

Period
2026—
Surface
MACOS
Role
SYSTEMS / PRODUCT
State
In the lab
ORIGIN / INTENT

DNS tools frequently expose the shape of a provider API instead of the intention of the person using it. That is manageable until accounts, delegated zones, credentials, and provider-specific record behaviour begin to overlap.

OrbitDNS explores the inverse: begin with the intended operation, show exactly what will change, preserve provider-specific truth, and make dangerous actions understandable before they become difficult to reverse.

THE QUESTION

Can a multi-provider DNS tool reduce cognitive load without hiding the details that make infrastructure changes safe?

THE METHOD

Normalise the workflow, not the truth. Provider capabilities stay explicit; credentials are validated in context; previews and diagnostics explain the real target before a mutation is allowed.

OBSERVED OUTPUT

Evidence of the work

  1. 01Multi-provider credential model
  2. 02Guided record operations
  3. 03Delegated-zone test environments
  4. 04Inspectable diagnostics and release checks
WHAT REMAINED TRUE

Field principles

Preview the blast radius.
A clean interface must not erase provider differences.
Diagnostics belong beside the action they explain.
macOSDNSProvider APIsDiagnostics