This will only work for unencrypted http traffic. As the majority of traffic is https today, this won't work. This is also the reason why we removed this blocking page some time ago.
Unfortunately the feature was removed and no longer works. It would be nice if a way to fix the issue with HTTPS connections could be fixed, but (although I do know how to code), I don't have the networking protocol understanding to contribute to resolving this issue.
Understood. I've done some quick searches but struggling to find an answer.. do you/anyone know if you can use a custom error page on Edge/Chrome etc for when you get the ERR ADDRESS INVALID error?
I just had a play with a few things, could this not be achieved by setting the blocking mode to IP_NODATA_AAAA and have the custom block page hosted on the main www directory?