Detect split-horizon DNS differences without leaking private zones
The same service name maps differently in two authorized network contexts.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- DNS · Privacy
Estimated field mix
- Networking60%
- Privacy engineering40%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional desktop sync client works on one office network but intermittently fails on another. Application retries hide whether DNS, IPv6, or transport limits are responsible.
Setup prerequisites
- Author synthetic packet traces and local IPv4/IPv6 endpoint doubles; use no third-party scanning or captured personal traffic.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Compare labeled resolver-context results.
- Report family, record class, and policy differences.
- Redact private names from shareable output.
Implementation constraints
- Use synthetic zone data and no external DNS queries.
Verification to include
- Compare two intentional split-horizon fixtures.
- Detect an unexpected public-context answer.
Deliverables
- Resolver comparison report.
Rollout and recovery
Review private results locally; share only the sanitized projection.
Value of the work
For the engineer: Practice layered network diagnosis and reproducible troubleshooting.
For the team: Produce precise support diagnostics that distinguish application defects from connectivity conditions.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.