Discussion in 'other software & services' started by ronjor, Sep 29, 2019.
By Catalin Cimpanu for Zero Day | September 29, 2019
Huh? Why it's mistake when Pi-Hole is a DNS-blocker? Does he confused this with AdGuard?
Well, AdGuardHome is also a DNS blocker which supports the ABP filter syntax which is, indeed, more flexible.
On the other hand Pi-hole supports regex: If you add, say, doubleclick.net in the Pi-hole Admin Console -> Blacklist and click "Add (wildcard)" this results in the following filter:
which blocks all sub-domains as well - similarly to adding
But he is right in saying that hosts files are very inefficient if it comes to ad blocking. That's why I'm using Pi-hole with an approach similar to this one.
Yup, I know Pi-Hole but admittedly don't know well about AdGuardHome. But even if it fully supports ABP syntax, that requires MITM capability to be efficient given nowadays most websites are https. And I don't wanna call such a blocker as DNS-blocker, that should rather be called filtering proxy. Or if it only can interpret ABP syntax but apply domain-level blocking (more likely scenario), then there's nothing wrong for Pi-Hole to drop the support.
Well, AdGuardHome only supports a limited set of modifiers. This actually causes problems with filter lists as the $third-party modifier is not supported right now.
That's surely a problem. If domains w/ $third-party are ignored, then filtering capability of the list will be significantly impaired. If blocked, then it will cause many FPs. Anyway if traffic is encrypted it can not distinguish 1st and 3rd party, so I think domain-level blocking is mostly enough for network-level blocker, as long as it supports subdomains as you've explained.
Separate names with a comma.