Reply to thread

Message

<blockquote data-quote="windscribe" data-source="post: 943271" data-attributes="member: 58131">You may be inventing scenarios that are non-existent. If you enable the Ads/trackers Filter, it will block Google Analytics/Firebase and other tracking specific domains. This will have no impact on Google Play services. Or you can block the whole &quot;Google&quot; service, which will block everything, and then you can manually create custom rules to bypass/redirect specific domains you still wish to work. Most specific rule wins if there is a conflict&nbsp; (*.google.com is blocked&nbsp; but you still wish for good-subdomain.google.com to load)As for the sites that force you to enable certain trackers, this is indeed a limitation of doing it through DNS. The DNS server doesn&#039;t know what you&#039;re on ESPN.com right now and wish for it to work there, but nowhere else. There are ways to do this, but it will be very brittle and require to store a lot of state. This is unadvisable.</blockquote>

[QUOTE="windscribe, post: 943271, member: 58131"] You may be inventing scenarios that are non-existent. If you enable the Ads/trackers Filter, it will block Google Analytics/Firebase and other tracking specific domains. This will have no impact on Google Play services. Or you can block the whole "Google" service, which will block everything, and then you can manually create custom rules to bypass/redirect specific domains you still wish to work. Most specific rule wins if there is a conflict (*.google.com is blocked but you still wish for good-subdomain.google.com to load) As for the sites that force you to enable certain trackers, this is indeed a limitation of doing it through DNS. The DNS server doesn't know what you're on ESPN.com right now and wish for it to work there, but nowhere else. There are ways to do this, but it will be very brittle and require to store a lot of state. This is unadvisable. [/QUOTE]

Verification