Reject alias loops and excessively deep resolution chains
A mistaken alias points back to the original hostname and exhausts lookup work.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Graph traversal · Resource bounds
Estimated field mix
- Networking70%
- Backend30%
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 internal API is moving to a new endpoint. The team assumes DNS changes are immediate and has no rehearsal for stale clients.
Setup prerequisites
- Create a local resolver simulator and two loopback service endpoints with synthetic DNS records; query no external infrastructure.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Track visited aliases.
- Bound chain depth and response size.
- Return a clear resolution failure without partial success.
Implementation constraints
- The resolver fixture remains local and read-only.
Verification to include
- Resolve a valid multi-hop chain.
- Reject a loop and an over-depth chain.
Deliverables
- Alias validation.
Rollout and recovery
Validate proposed record sets before applying the synthetic change.
Value of the work
For the engineer: Practice DNS semantics, migration timing, and network diagnosis.
For the team: Produce a migration plan that makes cache delay and endpoint compatibility explicit.
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.