the elephant in this room
the elephant in this room
Posted Jun 1, 2015 11:11 UTC (Mon) by ballombe (subscriber, #9523)In reply to: the elephant in this room by tpo
Parent article: Speed and bandwidth improvements with Firefox Tracking Protection
My /etc/host has (inter alia)
0.0.0.0 pagead2.googlesyndication.com
so no, I do not see it.
But at some point, Linux distributions are going to be complicit of user tracking by not
implementing some basic protection by default.
But how to do it while staying neutral is not obvious.
Posted Jun 1, 2015 12:09 UTC (Mon)
by tpo (subscriber, #25713)
[Link] (6 responses)
0.0.0.0 *.googlesyndication.com *.doubleclick.net
and so on? That's what I'd *really* like to do... however I don't know of any nice and elegant solution for this, short of some ugly local hack via a transparent DNS proxy.
Optimally there should be some resolver plugin that could be activated via nsswitch.conf, that does this, but AFAIK there is no such thing?
Posted Jun 1, 2015 12:27 UTC (Mon)
by anselm (subscriber, #2796)
[Link] (3 responses)
Dnsmasq can do this sort of thing and I personally would consider this reasonably nice and elegant. To sweeten the deal, dnsmasq can also perform other potentially useful services, like local caching of results, DNSSEC validation, and so on.
Posted Jun 1, 2015 12:54 UTC (Mon)
by tpo (subscriber, #25713)
[Link] (2 responses)
I know dnsmask a bit and I don't like it much for its complexity: it has the kitchen sink integrated, which is also reflected in its epic manpage. The problem at hand seems to be so trivial (blacklisting domains) that I'd expect that a solution would be accordingly trivial (a simple /etc/hosts.blacklist would do)...
Posted Jun 1, 2015 14:09 UTC (Mon)
by dmarti (subscriber, #11625)
[Link]
https://www.unbound.net/documentation/unbound.conf.html
I recently set up an Unbound internal DNS server and it works great.
The missing piece is a script that will parse the EasyPrivacy list and generate an "include"able file containing the correct "local-data" lines.
Posted Jun 1, 2015 15:56 UTC (Mon)
by kdave (subscriber, #44472)
[Link]
Posted Jun 1, 2015 16:07 UTC (Mon)
by kdave (subscriber, #44472)
[Link]
Posted Jun 1, 2015 19:05 UTC (Mon)
by dsowen (subscriber, #81373)
[Link]
I configure dnscache to send all requests for *.example.com to the local tinydns instead of resolving recursively from the DNS roots. I configure tinydns to be an authority for that domain (this is only inward-facing), then leave it with no A records for it. So a query for anything in *.example.com fails immediately, and I think that even the failure gets cached.
I have a short bash script to add a domain to both dnscache and tinydns and reload each. Whenever I catch a site misbehaving, I open up the browser's dev tools, track it down, and ban it. I don't mind ads, generally; ad servers that don't misbehave don't get banned.
When visitors use my network, they comment on how fast everything loads (but I have only 5 Mbps incoming) and how clean every site looks.
:)
domain name blacklisting
0.0.0.0 *.2o7.com
*t
domain name blacklisting
domain name blacklisting
domain name blacklisting
domain name blacklisting
domain name blacklisting
domain name blacklisting