mediumFix proposedLAN probeDHCP / DNS

DNS resolution failing

studio-imac failed to resolve 8 of 10 known domains (github.com, slack.com).

Home LAN · studio-imac (host probe) · 7/18/2026, 7:15:45 PM

Root-cause analysis

Diagnosed cause

DNS resolver unreachable or misconfigured

RCA confidence74%

Above the 70% threshold — a fix can be pre-formed.

Reasoning

DNS lookups are failing without a matching DHCP problem, isolating the fault to name resolution rather than addressing.

Generated by heuristic

Evidence trail

dns_resolution_failuresFailed DNS lookups (8/10): 8

Failed lookups with no DHCP-side failures point at the resolver.

Normalized telemetry (2)

Failed DNS lookups (8/10)8

DNS resolution latency850ms

Proposed fix

Flush the DNS resolver cache

Clear this host's DNS resolver cache so stale or poisoned entries are dropped and lookups re-resolve against the configured nameservers. Safe and non-disruptive — it does not drop the network connection.

risk: lowprobe.dns.flush_resolver_cache

Exact calls that will run

1. Flush the Windows DNS resolver cache

POST host:ipconfig /flushdns

Demo: try the approve flow

Click below to watch this exact playbook execute step by step. Read-only and scripted, nothing real is touched.