You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally coming from Netguard, I am missing the feature which clearly links a DNS request to an app in the DNS logs.
While you can see which app actually connected to an IP address in the network logs, you can't for example see if an app:
An app requests many malicious DNS lookups
DNS lookup gets blocked by RethinkDNS since it's a blocked domain (tracking/ads/malware etc)
You can see that some app tried to connect to this blocked domain, but you can't see which app it was
The DNS logs have many entries that this domain was blocked, but since it was blocked the app can't connect to it, which means it does not show up in the network logs at all
If you try to figure out which app is requesting all those malicious domains (e.g. to delete it since you don't want such an app on your device), it's currently difficult to determine the causing app
Since Netguard is able to match a blocked domain request to the app requesting it, and Rethink can already match connections to apps, I believe this should be possible to implement in RethinkDNS as well.
I suggest to add the app's name (and maybe its icon?) either to the main DNS log page or at least to the details which pop up when clocking on a logged DNS request.
What do you think?
The text was updated successfully, but these errors were encountered:
Originally coming from Netguard, I am missing the feature which clearly links a DNS request to an app in the DNS logs.
While you can see which app actually connected to an IP address in the network logs, you can't for example see if an app:
Since Netguard is able to match a blocked domain request to the app requesting it, and Rethink can already match connections to apps, I believe this should be possible to implement in RethinkDNS as well.
I suggest to add the app's name (and maybe its icon?) either to the main DNS log page or at least to the details which pop up when clocking on a logged DNS request.
What do you think?
The text was updated successfully, but these errors were encountered: