- Project scope
- 10 tickets / 3 phases
- Total focused work estimate
- 25h 30m + setup
- Suggested stack
- TypeScript · DNS fixtures · HTTP
Recommended next stepStart with BDNS-101
Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away
Practice DNS semantics, migration timing, and network diagnosis.
What the team gains
Produce a migration plan that makes cache delay and endpoint compatibility explicit.
Before you start
- Create a local resolver simulator and two loopback service endpoints with synthetic DNS records; query no external infrastructure.
Delivery agreement
Deliver local DNS simulations and a cutover report; modify no real DNS records.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases
- PHASE 1
Define record and cache semantics.
- PHASE 2
Handle stale clients and lookup failures.
- PHASE 3
Choose timing and recovery controls.
Model DNS responses
Define record and cache semantics.
BDNS-101Entry ticket; project setup still required BDNS-102Depends on BDNS-101Estimated field mix
- Networking60%
- Performance engineering40%
BDNS-103Depends on BDNS-102Estimated field mix
- Networking80%
- Site reliability20%
Rehearse endpoint changes
Handle stale clients and lookup failures.
BDNS-104Depends on BDNS-102 BDNS-105Depends on BDNS-102, BDNS-103Estimated field mix
- Networking60%
- Site reliability40%
BDNS-106Depends on BDNS-105Estimated field mix
- Networking40%
- API design40%
- Quality engineering20%
BDNS-107Depends on BDNS-104, BDNS-106Estimated field mix
- Networking70%
- Site reliability30%
Review cutover
Choose timing and recovery controls.
BDNS-108Depends on BDNS-105, BDNS-106, BDNS-107Estimated field mix
- Networking40%
- Distributed systems30%
- Site reliability30%
BDNS-109Depends on BDNS-108Estimated field mix
- Networking80%
- Quality engineering20%
BDNS-110Depends on BDNS-109Estimated field mix
- Networking70%
- Site reliability30%
Use this project
CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.