"Instead you need a gigantic list of filter rules, one for each domain, making loading web pages slower."
By not using recursive DNS, including open resolvers or other third party DNS providers, I avoid this problem. I do not need to maintain a list of domains to block,^1 I only need to maintain a list of domains for hosts that I actually want to access. I do not even make remote DNS lookups because generally I already have the DNS data stored (gathered in bulk beforehand), so the web becomes faster, not slower. One of the requirements for the web to suck the way it does, and for so-called "tech" companies to proliferate by collecting data and selling ad services, is that the web browser and webpages must be give free reign to resolve any domain name. IME over nearly 20 years of controlling own DNS, restricting that ability makes the web instantly readable, even so-called "dumpster fire" webpages.
1. AFAICT no one actually does this anyway. They delegate the task to third parties, "blocklist" maintainers.
By not using recursive DNS, including open resolvers or other third party DNS providers, I avoid this problem. I do not need to maintain a list of domains to block,^1 I only need to maintain a list of domains for hosts that I actually want to access. I do not even make remote DNS lookups because generally I already have the DNS data stored (gathered in bulk beforehand), so the web becomes faster, not slower. One of the requirements for the web to suck the way it does, and for so-called "tech" companies to proliferate by collecting data and selling ad services, is that the web browser and webpages must be give free reign to resolve any domain name. IME over nearly 20 years of controlling own DNS, restricting that ability makes the web instantly readable, even so-called "dumpster fire" webpages.
1. AFAICT no one actually does this anyway. They delegate the task to third parties, "blocklist" maintainers.