Omit Telemetry DNS traffic from the DNS query count
I would estimate that about 60% or more of my monthly queries being tabulated by nextDNS are either Google telemetry (beacons.gvt) or Microsoft "msftconnecttest." While these can be turned off & blocked, they serve a purpose when you have Chromebooks, Android phones and Windows workstations on your network.
There should be a way to omit these perpetual, generally benign queries from the overall count, which would give a more valid metric against the free 300,000 queries a month.
1 reply
-
Sadly, they are genuine requests made by your device. And those requests need to be answered and counted into your monthly query allowance.
A solution would be to implement your own dns locally, which would remember the dns logs and answers on himself. But some occasional request will be still be sent (time out memory) to refresh the database and restore eventual move links. The cons are by doing so, you defeat the purpose of having nextDNS in the first place. Since you can implement the blocking list and other protections mechanisms directly on the localized dns.
Content aside
-
1
Likes
- 11 hrs agoLast active
- 1Replies
- 44Views
-
2
Following