NextDNS · home network device coverage

21 JUNE 2026 · window -24h

At a glance

• ❌ RED — 51.3% of queries from unidentified devices (52,688 of 102,646)
• 6 named device(s) accounting for 49,958 queries
• Threshold: ≤5% green · 5-20% amber · >20% red

Why this matters

Unidentified traffic is the home-network equivalent of an unaccounted-for log line — something is making DNS queries and we can’t tell which device it is. Most often it’s: a router doing recursive resolution (forward to NextDNS but don’t tag with device id), an IoT device NextDNS can’t fingerprint, or a device that’s deliberately or accidentally bypassing the profile (guest Wi-Fi, plain-DNS escape, VPN flip).

The fix is one of: name the device in the NextDNS dashboard so it stops rolling up under UNIDENTIFIED, or configure the router to forward per-client DNS rather than recursing centrally.

Device breakdown

What to do next

1. Open https://my.nextdns.io/9bb389/analytics/devices and look at the UNIDENTIFIED bucket.
2. Cross-reference with router/DHCP leases — which IP is sending the queries?
3. If it’s the router itself: configure per-client DNS forwarding (LAN clients query NextDNS directly via DHCP option 6, not through the router’s recursive resolver).
4. If it’s a real device: name it in the NextDNS dashboard so it leaves the unidentified bucket.

_{Generated by dare_nextdns_audit.py --check device_coverage}