Portal | Level: L2: Operations | Topics: DNS, Kubernetes Networking | Domain: DevOps & Tooling

Ops Archaeology: The 5% That Can't Resolve

File	Purpose
briefing.md	Scenario briefing with artifacts
hints.md	Progressive hints (timed)
answer_key.md	Full solution and skills tested

Ops Archaeology exercise — see ops-archaeology index for context.

Pages that link here

• Answer Key: The 5% That Can't Resolve
• DNS Resolution Taking 5+ Seconds Intermittently
• DNS Split-Horizon Confusion
• Ops Archaeology: Reverse-Engineering Production Systems
• Runbook: DNS Resolution Failure
• Symptoms
• Symptoms
• Symptoms: Grafana Dashboard Empty, Prometheus Scrape Blocked by NetworkPolicy

---

Wiki Navigation

Prerequisites

• Networking Deep Dive (Topic Pack, L1)

Related Content

• Case Study: CoreDNS Timeout Pod DNS (Case Study, L2) — DNS, Kubernetes Networking
• Runbook: DNS Resolution Failure (Runbook, L1) — DNS, Kubernetes Networking
• API Gateways & Ingress (Topic Pack, L2) — Kubernetes Networking
• AWS Route 53 (Topic Pack, L2) — DNS
• Case Study: CNI Broken After Restart (Case Study, L2) — Kubernetes Networking
• Case Study: Canary Deploy Routing to Wrong Backend — Ingress Misconfigured (Case Study, L2) — Kubernetes Networking
• Case Study: DNS Looks Broken — TLS Expired, Fix Is Cert-Manager (Case Study, L2) — DNS
• Case Study: DNS Resolution Slow (Case Study, L1) — DNS
• Case Study: DNS Split Horizon Confusion (Case Study, L2) — DNS
• Case Study: Grafana Dashboard Empty — Prometheus Blocked by NetworkPolicy (Case Study, L2) — Kubernetes Networking