NextDNS · home network device coverage
7 JUNE 2026 · window -24h
At a glance
- ❌ RED — 60.0% of queries from unidentified devices (85,686 of 142,728)
- 8 named device(s) accounting for 57,042 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
| Device | Queries | Share |
|---|---|---|
unidentified (__UNIDENTIFIED__) |
85,686 | 60.0% |
| Apple TV Upstairs | 29,751 | 20.8% |
| iPhone 13 Pro | 11,738 | 8.2% |
| Audrey iMac M1 | 11,482 | 8.0% |
| Lounge TV | 3,720 | 2.6% |
| dans-macbook-14–pro | 258 | 0.2% |
| iphone-13-pro-max | 44 | 0.0% |
| Dan’s M2 | 33 | 0.0% |
| vm-asia-gcp | 16 | 0.0% |
What to do next
- Open https://my.nextdns.io/9bb389/analytics/devices and look at the UNIDENTIFIED bucket.
- Cross-reference with router/DHCP leases — which IP is sending the queries?
- 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).
- 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