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
I use your filtering DNS servers on my Android smartphone (settings / network and internet / private DNS, I use "base.dns.mullvad.net").
With such settings, DNS normally blocks tracking in browsers but also blocks applications internal tracking.
However, if it is efficient to block data sent by applications to almost all tracking companies, it is not efficient to block data sent by applications to Google.
Your GitHub website, https://github.com/mullvad/dns-blocklists, shows that you use firebog and hagezi lists, and your own very short list. Though firebog and you list do include some filters against Google tracking, that's not enough to prevent applications to send data to Google.
This can be detected by installing "DuckDuckGo Private Browser" application on Android and by activating its applications internal tracking protection. As an example, with my bank application, DuckDuckGo detects (and blocks) data sent to Google and 4 other tracking companies; but, when "base.dns.mullvad.net" is used as private DNS, DuckDuckGo detects only data sent to Google.
Where is the problem, since DuckDuckGo application tracking protection and Mullvad base filtering DNS can do the job jointly?
DuckDuckGo is obliged to act as a pseudo VPN in Android settings, and prevents the use of a "true" VPN. So, if I used Mullvad VPN on Android, and if I selected "base.dns.mullvad.net" as DNS server within Mullvad settings, I would lose the capability to use DuckDuckGo applications tracking protection and applications would send tracking data to Google.
Note that, in this use case (Mullvad VPN on Android), it is not possible to add an extra filter such as uBlock Origin to complete applications internal tracking protection, it just relies on your filtering DNS server.
1st suggestion: to reinforce Google anti-tracking.
Another "big tracker" is Facebook; but firebog list includes only one facebook filter.
2nd suggestion: to reinforce Facebook anti-tracking.
What are the issues you need support with?
Hi,
I use your filtering DNS servers on my Android smartphone (settings / network and internet / private DNS, I use "base.dns.mullvad.net").
With such settings, DNS normally blocks tracking in browsers but also blocks applications internal tracking.
However, if it is efficient to block data sent by applications to almost all tracking companies, it is not efficient to block data sent by applications to Google.
Your GitHub website, https://github.com/mullvad/dns-blocklists, shows that you use firebog and hagezi lists, and your own very short list. Though firebog and you list do include some filters against Google tracking, that's not enough to prevent applications to send data to Google.
This can be detected by installing "DuckDuckGo Private Browser" application on Android and by activating its applications internal tracking protection. As an example, with my bank application, DuckDuckGo detects (and blocks) data sent to Google and 4 other tracking companies; but, when "base.dns.mullvad.net" is used as private DNS, DuckDuckGo detects only data sent to Google.
Where is the problem, since DuckDuckGo application tracking protection and Mullvad base filtering DNS can do the job jointly?
DuckDuckGo is obliged to act as a pseudo VPN in Android settings, and prevents the use of a "true" VPN. So, if I used Mullvad VPN on Android, and if I selected "base.dns.mullvad.net" as DNS server within Mullvad settings, I would lose the capability to use DuckDuckGo applications tracking protection and applications would send tracking data to Google.
Note that, in this use case (Mullvad VPN on Android), it is not possible to add an extra filter such as uBlock Origin to complete applications internal tracking protection, it just relies on your filtering DNS server.
1st suggestion: to reinforce Google anti-tracking.
Another "big tracker" is Facebook; but firebog list includes only one facebook filter.
2nd suggestion: to reinforce Facebook anti-tracking.
The use of this list, https://gitlab.com/quidsup/notrack-blocklists/raw/master/notrack-blocklist.txt, in complement with the trackers lists you use now, might be an answer to both suggestions.
Regards,
MN
Additional Information
No response
The text was updated successfully, but these errors were encountered: