JarvisOS HomeLab status
No signal

Public DNS

No signal critical tier-0 DNS external

Authoritative public DNS. Controls whether published routes resolve at all.

Last heartbeat
never
Signal source
probe
Recovery readiness70/100
Recovery procedure →

Why it is no signal

Availability class

Fleet-fatal · target 99.5%

Authoritative public DNS: decides whether published routes resolve at all.

Class
tier-0 Fleet-fatal: loss stops the estate or risks data. Everything else waits.
RTO (declared)
RTO (achievable)
RPO
State
none
Redundancy
vendor HA
Failover
vendor
Failure domain
fd-edge-dns

Health check: authoritative resolution probe every 900s — proves the expected records are returned by the authoritative nameserver. Observed independently of the service.

Without it: Nothing published resolves. Clients with warm caches keep working until TTLs expire, which is why a correct fix can still look broken for minutes. LAN access by IP is unaffected.

Full classification and SLOs →

Dependencies

blast radius: 1
Depends on ISP Uplink
Depended on by Caddy (reverse proxy)