FAQ – Bypassing the Content Filter

I am unable to bypass the Content Filter, please advise?

 

There are two possible reasons you are unable to bypass the Content Filter.

Reason 1

The Bypass Rule is below the DNS intercept in the NAT rules.  If this is the case, then it is essential that you insert the Bypass Rule  above the DNS Intercept in the NAT rules.

This ensures we do not intercept and handle DNS requests for bypassed clients on the Mikrotik DNS server which forwards to the cloud.

Reason 2

The DHCP server should serve our public DNS servers, catblock-v2-ns1.lucidview.net – catblock-v2-ns7.lucidview.net as DNS servers. Or rather, the IPs below
catblock-v2-ns1.lucidview.net has address 129.232.134.92
catblock-v2-ns2.lucidview.net has address 95.85.22.11
catblock-v2-ns3.lucidview.net has address 159.203.96.234
catblock-v2-ns4.lucidview.net has address 178.62.244.63
catblock-v2-ns5.lucidview.net has address 197.189.204.177
catblock-v2-ns6.lucidview.net has address 159.65.92.219
catblock-v2-ns7.lucidview.net has address 159.65.92.244
 
This ensures the bypass hosts use our open DNS resolvers (so we still log the DNS request for reverse lookup) but do not get blocked by the content filter.