Recover: Public DNS
No signal criticalAuthoritative public DNS. Controls whether published routes resolve at all.
- Owner
- homelab-operator
- Target RTO
- not defined
- Last heartbeat
- never
- Dependent entities
- 1
Recovery readiness70/100
Procedure
Read fully before acting.- DNS is managed outside JarvisOS. Record changes are a human action, never automated from here.
- Propagation lag means a correct record can still look broken for minutes — verify against the authoritative nameserver.
- Certificate renewal depends on this; DNS failures surface as TLS failures a day or two later.
Bring-up order
Dependencies first — starting out of order is a common second incident.- ISP Uplink Dependency
- Public DNS DNS target
What this affects
Impacted if this stays down, or while you restart it.
Downstream
Caddy (reverse proxy)
Readiness breakdown
- Documented runbook 20 pts
- Vendor-managed (no local backup expected) 50 pts
- No failover target configured 30 pts