On Sun, 2021-01-24 at 09:01 +0000, J.Witvliet--- via users wrote:
Didn’t know you could do that.
I tried it, but my bind complained that I was not authoritive.
(Right now there is a dns-storm against the USA-IRS)
To be honest, I wouldn't advise anyone to start running their own BIND
server unless you felt like learning how to do so. There are simpler
ways to make browsing less painful (scriptblockers, ad-blockers,
privacy proxies, etc), that are just a browser plug-in to install.
But, for anyone who's already got BIND running, adding a bunch of lines
like the following to the /etc/named.conf file:
zone "doubleclick.net" { type master; file "dead.zone"; };
zone "doubleclick.com" { type master; file "dead.zone"; };
zone "adwords.google.com" { type master; file "dead.zone"; };
zone "googlesyndication.com" { type master; file "dead.zone"; };
zone "googleservices.com" { type master; file "dead.zone"; };
zone "googleadservices.com" { type master; file "dead.zone"; };
Which all load up a barebones dead.zone file from where all your other
zone files are stored (typically /var/named/), just like this:
$TTL 10
@ IN SOA ns.localdomain. hostmaster.mail.localdomain. (
42 ; serial
20 ; refresh
20 ; retry
20 ; expire
20 ; ttl
)
IN NS ns.localdomain.
This instantly kills traffic to any domain, and sub-domain, that you
list in the named.conf, how I've shown above. It kills it for anything
that uses the web, not just your web browser. Your mail client, your
smart TV, etc.
The zone file acts like a wildcard does-not-exist answer to all related
queries.
--
uname -rsvp
Linux 3.10.0-1160.11.1.el7.x86_64 #1 SMP Fri Dec 18 16:34:56 UTC 2020 x86_64
Boilerplate: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.