Bind

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.

Move to the directory that contains the Bind configuration files. By default, the folder should be located at the following path:

The file we need to change is the named.conf.options file. Open it in your preferred text editor with sudo privileges:

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.

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:

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:

If there are no syntax errors in your configuration, the shell prompt will terminate immediately without displaying any output.

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.

We are done! You should now have your Bind server properly configured to start filtering content and protecting your network from malware.