Recover: Internal DNS
No signal importantResolves 10.10.0.0/24 names for LAN services.
- Owner
- homelab-operator
- Target RTO
- 20m
- Last heartbeat
- never
- Dependent entities
- 0
Recovery readiness50/100
Procedure
Read fully before acting.- Clients cache aggressively — a fixed resolver can still look broken until TTLs expire.
- Use IP addresses directly during recovery rather than waiting on DNS.
Bring-up order
Dependencies first — starting out of order is a common second incident.- Home1 Node
- Internal DNS DNS target
Failover targets
mode: automatic-
Secondary resolver on VIN answers when Home1 is unreachable.
Readiness breakdown
- Documented runbook 20 pts
- No backup configured 50 pts
- Healthy failover target available 30 pts