unbound-block-hosts

I'm using this whenever I have a working server lying around. Unbound works great. https://github.com/gbxyz/unbound-block-hosts

There is also this perl script for generating a DNS based blocklist for unbound out of Dan Pollock's hosts file. https://github.com/jodrell/unbound-block-hosts

Adding another vote of confidence for running your own local DNS resolver with a block list. I use this script to generate a compatible hosts list for unbound: https://github.com/jodrell/unbound-block-hosts It's not terribly sophisticated, but every few weeks or whatever I just run this again: $ ./unbound-block-hosts --file=/opt/brew/etc/unbound/local-blocking-data.conf $ killall -HUP unbound

I completely agree re: password managers. Lots of options and competition but nobody has yet really, really nailed it. I eventually got many not-so-technical family members and friends to adopt Dashlane - which is easy to use and provides great support. > 2. I do that. In addition I use this: http://winhelp2002.mvps.org/hosts.htm That's a good idea - you can also configure a local bind/dnsmasq/unbound server to block based on these lists with ACL's (sure if you google each you'll find tutorials, like this one: https://github.com/jodrell/unbound-block-hosts) Some of the better home router distros will also do this at the local network level

Yes, unbound is great—I run it on my local machine with a list of ad servers to block. I use this little script to download and convert the Someone Who Cares hosts list to unbound format[0] every few weeks. BTW, the pgl.yoyo.org list is available[1] in Unbound format since a few months ago[2]. [0] https://github.com/jodrell/unbound-block-hosts [1] https://pgl.yoyo.org/adservers/serverlist.php?hostformat=unb... [2] https://pgl.yoyo.org/adservers/news.php?#unbound

DNS blocking works quite well. It's also very effective if you can set it up on your gateway so that it blocks ads/malware for all devices (PCs, phones, tablets ... even your guests will get adblocking for free!). However, while the /etc/hosts trick works I don't think it's the best way. The reason is that while parsing a plaintext file is easy and generally fast, it doesn't scale well especially when you have to traverse several megabytes of it for _every_ DNS request. The way I have done it is by installing unbound[0]. If you aren't using something else like dnsmasq, you will notice a speedup from the DNS caching alone. While unbound isn't supposed to serve authoritative answers (i.e.: don't use it to manage your zone) the possibility is there. The unbound-block-hosts script[1] can be used to convert Dan Pollocks' hosts file to the appr

A bit of a late reply, but I have switched to using this on my home LAN now: https://github.com/jodrell/unbound-block-hosts Basically, a Perl script to massage the data from Dan Pollock's list into a format suitable for unbound (http://www.unbound.net/)

FWIW, all of these are in Dan Pollocks ad blocking hosts list: http://someonewhocares.org/hosts/ On my network, I use the following script to convert the hosts file he provides into an unbound config file which I include from my main unbound config, using this script: https://github.com/jodrell/unbound-block-hosts This provides ad blocking for my entire network, including my smart tv.