AH is one of the larger supermarkets in The Netherlands. They have a mobile app where you can browse their products, create your groceries shopping list, etc. static.ah.nl is what their mobile app uses to fetch the pictures of all the products they are offering.
I’ve added it to the allowed list as well, and still it’s being blocked by Blokada DNS.
As an aside: not a Blokada issue, but it is annoying how often valid domains are added to the DuckDuckGo tracker list.
Agreed, that it sometimes needs more than one entry to allow an app to work.
However that is not the case here. Here we have the issue that even though static.ah.nl has been added to “Allowed” it continues to be blocked by Blokada. See screenshots.
It will take a while until the setting is applied. Stopping and restarting Blokada speeds things up.
Still there is the option to test another endpoint.
Thanks Guido for explaning where the url static.ah.nl is used for!
When I disable the DuckDuckGo Tracker Radar blocklist, the site static.ah.nl is available.
I have another example of a site that is blocked by the DuckDuckGo Tracker Radar blocklist, but is allowed by me: res-h1.cdn.office.net (used by Office 365). But now it is blocked.
This used to work, because this url has been on the allowed list for some time. The same goes for static.ah.nl.
So looks like something has changed in the Blokada application or blocklist?
For now I will disable DuckDuckGo Tracker Radar blocklist.
The issue would happen for all domains which contained CNAME records that in turn were present in the blocklist.
For example static.ah.nl points to static.ah.nl.edgekey.net which in turn is blocked in the DDG list, for these cases your custom exception would not be respected where it should have been.
I appreciate the feedback and detailed examples you provided, keep it coming!