Home labs & practical projects
Separate a DNS failure from a connectivity failure
A project to do with your own tools, with guidance on what to create and capture.
What you could create
A user can reach a test service by address but not by name. Another machine cannot reach it either way. Both tickets say “the network is down”.
| Evidence | What to capture |
|---|---|
| Two worked troubleshooting records | Show the inputs, scope and decisions behind this record. Tests separate name resolution from packet delivery. |
| Layered diagnostic decision tree | Include the evidence supporting your conclusion. The final validation includes both address-based and name-based access. |
What you'll need
Local lab
Use a network simulator or two lab VMs and a harmless local service. Create one reversible resolver error and one separate connectivity issue.
Project record
Keep the working files for two worked troubleshooting records and record assumptions as you go.
Current reference material
Use the linked provider resources to verify the features, access terms and version relevant to your project.
Access & cost
Uses your own computer. Confirm hardware capacity, software licences and download terms before setup.
Use disposable VMs, containers or a simulator. Keep the lab separate from your everyday machine and work network.
Suggested milestones
- 1
Plan and investigate
Document address configuration, gateway reachability and name-resolution results.
- 2
Develop your approach
Trace the two failures through distinct diagnostic paths.
- 3
Verify and explain
Correct each fault and explain why the same symptom needed different fixes.
Useful resources
Use these resources to deepen your understanding and check key details.
Review the current provider requirements and relevant subject areas.
Check relevance, platform versions and current access terms.
Find relevant providers and check features, access requirements and costs.
A useful starting point
Use a network simulator or two lab VMs and a harmless local service. Create one reversible resolver error and one separate connectivity issue.
What a good result looks like
- Tests separate name resolution from packet delivery.
- The final validation includes both address-based and name-based access.
Finish the project
Save sanitised evidence, then remove the lab instances or revert to the clean snapshot. Remove temporary accounts and credentials.
Independent home-project guidance, not an official vendor lab or a claim of complete exam coverage. Use your own tools and label the work accurately.