A couple of months ago I set up DNS filtering for our home network using https://github.com/hagezi/dns-blocklists.git and the pro.txt list specifically. Did it with the full expectation that it will cause issues and I will have to dedicate some time to fixing those for the family as everyone is online a lot.

In fact it has not caused a single thing we use to stop working, except regularly causing various things to log failures to track. Some site tries to redirect me to ads, they fail to load. VSCode tries to send stats (?) to Microsoft and logs error in reaching it (but keeps working). All sorts of Windows and Apple tracking gets nuked too, about 1 in 5 dns requests gets killed in a sample of about 8 million requests.

Loving it!

Reply to this note

Please Login to reply.

Discussion

noice! What level did you choose?

Cheers. I should have read that in your first post 🥺

Misspoke about Apple tracking - they must be hiding it in other traffic. Here's the top 15:

426562 | logs.netflix.com

121690 | eu-teams.events.data.microsoft.com

104990 | teams.events.data.microsoft.com

89999 | incoming.telemetry.mozilla.org

83716 | eu-mobile.events.data.microsoft.com

78706 | browser.events.data.microsoft.com

66120 | euc-excel-telemetry.officeapps.live.com

56860 | fls-eu.amazon.co.uk

56618 | eu-office.events.data.microsoft.com

37358 | posthog.element.io

28540 | unagi.amazon.co.uk

22030 | data.pendo.io

20506 | star-randsrv.bsg.brave.com

19130 | mars.prod.ads.prod.webservices.mozgcp.net

16330 | browser.pipe.aria.microsoft.com

Kinda disappointing that element and brave made it into the list above.