In this article
This Issue is Resolved
The DNSFilter team released a fix for this issue on 3 December 2024.
What we know
The issue causing inaccurate Resolver Location data to appear on the Insights Reporting page has been resolved. Our engineers successfully connected the service regions data to the dashboard to ensure proper synchronization.
As an added precaution, the workaround will remain available in case the region does not sync as expected.
How to work around the issue
The device's Dev Tools will show the correct region for the traffic.
- From Insights, open the Dev Tools Network tab (Ctrl-Shift-I in Windows; ⌥-⌘-I in Mac)
- Filter for FQDN
- Select
query_logs?... - Tab to Preview
- Expand
Values - Expand any of the values to find the service region of the DNS traffic
Comments
1 comment
This issue is resolved.
Please sign in to leave a comment.