Check before you change.
A fresh read checks the current server state and dependencies before a supported change begins.
The workflow
Confidence comes from
knowing the state.
Inspect what exists, plan a supported change, and verify what happened.
Read the result back.
Verify changes against a fresh snapshot. Keep a record of the operation and its outcome.
Keep a way back.
Use journaled operations, supported rollback, and fresh-state recovery analysis when a change needs attention.
Understand what’s there.
Analyze the loaded DNS policy configuration without changing it. Review findings before planning your next step.
See the differences.
Compare snapshots from different servers to review configuration differences before making a change.
Follow configuration over time.
Review differences between consecutive saved snapshots, with object-level changes and Health comparisons.
Professional workflows
Controlled changes to DNS policy configuration.
- Create Query Policies, Client Subnets, and Recursion Scopes.
- Edit supported Client Subnet and Recursion Scope settings.
- Enable or disable Query Policies.
- Use controlled policy replacement and supported deletion.
- Preview Segment Wizard plans, then apply with Professional.
A deliberate scope
Know what’s included.
ConfigWitness DNS manages a supported set of Microsoft DNS policy configuration workflows. It does not manage DNS zones or records, DHCP, Active Directory, or cloud DNS.
Compare uses saved or current snapshots. Drift History uses snapshots you have collected; it is not background monitoring or an exact record of when external changes occurred.
Rollback applies where the supported workflow can safely reverse a change. Review fresh-state recovery analysis before acting on an interrupted operation.