Generic guide to enable cloud filtering

overview first, check whether your internet connection uses a static or dynamic ip address to find out this information, we recommend contacting your internet service provider if you have a dynamic public ip, you must perform an initial synchronization step outlined in section one if you have a static ip, your ip is already fixed and you can skip directly to section two of this guide configuration with a dynamic public ip on networks with dynamic public ips, you must first set our cloud addresses as the primary and secondary dns on the main router or firewall installed on your network primary dns 185 236 104 104 secondary dns 185 236 105 105 next, you need to configure the dynamic dns service on your device by setting the following synchronization parameters service provider leave this field blank or select a custom provider please refer to our dedicated custom service articles if your device does not allow manual typing username enter the specific username assigned to your dynamic network inside the dashboard password enter the specific password assigned to your dynamic network if everything has been set up correctly, you will be able to see your public ip inside the networks menu, accompanied by a green dot indicating that the synchronization was successful otherwise, you can perform a manual connection test by clicking the device connection test button once synchronized, proceed to the next step dns configuration on the internal network you can enforce the filter on your internal network devices using one of the following methods, depending on your specific it infrastructure transparent redirection create nat rules in your firewall management to intercept all traffic on port 53 and redirect it to our ips this way, even if users manually change the dns on their internal devices, their traffic will still be safely filtered port blocking create strict rules on your firewall to block all outbound traffic on port 53, except for queries directed specifically to our cloud ips dhcp distribution configure our dns addresses directly on your dhcp server the server will automatically distribute them to the different connected devices, ensuring they are all filtered immediately router ip forwarding configure our dns on your main router or firewall then, set the local ip address of that specific router as the only dns on the internal devices make sure you use only this local ip and do not set any secondary dns address internal dns server if your network relies on an internal dns server like a windows domain controller, you can configure our ips in the dns settings by setting up a forwarding server this setup allows you to keep your local server ip as the only dns on the various network devices, ensuring you can continue to resolve the hostnames of your internal machines without bypassing the cloud filter manual setup if it is not possible to enable a dhcp server or a local dns, you must configure our dns addresses manually inside the network settings of each individual device