Read-only demo. A simulated multi-vendor fleet. Detection and fixes are illustrative; nothing here touches a real network.
Fault Board
highFix proposedMerakiDHCP / DNS

DNS resolution failures on HQ - Floor 2

Clients on HQ - Floor 2 cannot resolve hostnames.

HQ - Floor 2 · 5/29/2026, 8:56:44 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 (5 min): 320

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

Normalized telemetry (1)
Failed DNS lookups (5 min)320
Proposed fix

Expand DHCP scope and correct DNS

Widen the DHCP lease range on the affected VLAN to relieve pool exhaustion and reset the configured DNS servers to the network default, then verify lease issuance.

risk: mediummeraki.dhcp.expand_pool_and_fix_dns
Exact calls that will run
1. Expand DHCP lease range on the appliance VLAN for network N_hq
PUT /networks/N_hq/appliance/vlans/{vlanId}
2. Reset DNS nameservers to the upstream resolver default
PUT /networks/N_hq/appliance/vlans/{vlanId}

Approving is disabled in the read-only demo.