NextDNS is not blocking anymore but logs shown as blocked
NextDNS seems to be buggy for my instance; meaning is showing that requests were blocked but in reality they will not be blocked / they will open on my device.. I see that the DNS is effectively/correctly used in GUI (I can see my requests from all devices) and also can see the webpage is blocked as it should in LOG - so configuration seems to be fine from my side.. But in reality it isn't blocked. The page opens and loads normally on my device.. So I assume that NextDNS resolves the DNS request; nevertheless the request should be blocked.. I only have the issue for one of my instances, for other instances/ profiles its working fine.. Both use DoT.
6 replies
-
Also Adblock test https://d3ward.github.io/toolz/adblock.html is showing that nothing is effectively blocked; but in NextDNS GUI/LOG the requests are shown as blocked.. Strange.
-
Looks like it’s working again.. Without change. lol. Blocked pages in Log are now really blocked ;).
-
Please make sure Apple Private Relay is off, or if you want to turn it on, make sure the block page feature is off on NextDNS.
-
If you check the "compatibility" page of this tool, they explain their test does not work if our blockpage capability is enabled:
-
Hi. Both were disabled. I was not using Private Relay & Blockpage..
Anyhow. As described above the problem is already solved without change from my side. It „magically“ worked again after a short time
. I think there were some temporary issues on your side. Now it’s working Again ;). And entry’s shown in log as blocked are really blocked ;).
Content aside
- 6 mths agoLast active
- 6Replies
- 254Views
-
2
Following