Bind

overview if you are using bind as your internal dns server and want to forward all incoming requests to our cloud servers, you can easily enable our malware protection and content filtering features please follow the steps below to configure the forwarding rules for more information on how bind works, you can visit their official website before proceeding with this guide, you must register your public ip address in your dashboard only registered ip addresses can use the malware protection and content filtering features on their network you can do this by navigating to your control panel and accessing the networks section configuration steps locate the configuration folder move to the directory that contains the bind configuration files by default, the folder should be located at the following path cd /etc/bind open the options file the file we need to change is the named conf options file open it in your preferred text editor with sudo privileges sudo nano named conf options add the forwarders block within the options block, we need to create another section called forwarders this new block will contain the ip addresses of the dns servers to which we want to forward all requests you must enter our primary and secondary ips set the forward directive now we need to set the forward directive to the value "only" right below the forwarders block this ensures your server will automatically forward all requests and will not attempt to resolve them on its own when finished, your configuration file should look exactly like this routeros options { directory "/var/cache/bind"; forwarders { 185 236 104 104; 185 236 105 105; }; forward only; dnssec validation auto; auth nxdomain no; # conform to rfc1035 listen on v6 { any; }; }; verify the syntax save and close the file once you are done to check if you have done everything correctly, you can use the built in tools provided by bind to verify the syntax of the configuration files simply type the following command in your terminal sudo named checkconf if there are no syntax errors in your configuration, the shell prompt will terminate immediately without displaying any output restart the service finally, you need to restart the bind daemon to implement the new changes you can do this with the following command note that the command below uses bind 9 please replace the service name with the specific version you are currently using if it is different sudo service bind9 restart we are done! you should now have your bind server properly configured to start filtering content and protecting your network from malware