Most routers and firewalls will allow you to force all DNS traffic over port 53, thus requiring everyone on the network to use the DNS settings defined on the router/firewall (in this case, Barracuda DNS nameserver). The preferred recommendation is to forward all DNS requests to go to the Barracuda IP address listed below. This way, you simply forward users' DNS requests without them knowing, instead of having the possibility of someone manually configuring DNS and having it not work.
Create two firewall rules to only allow DNS (TCP/UDP) to Barracuda DNS nameservers and restrict all other DNS traffic to any other IP addresses. Add this policy to the firewall that is at the furthest edge of your network. The rules would look something like this:
ALLOW TCP/UDP IN/OUT to <Barracuda DNS nameserver IP> on Port 53
BLOCK TCP/UDP IN/OUT all IP addresses on Port 53
The first rule takes precedence over the second rule. Put simply, any requests to Barracuda will be allowed and any requests to any other IP address will be blocked.
- Depending on your firewall configuration interface, you may need to set up a separate rule for each of these protocols, or one rule which covers both.
- The rule can be applied on either the firewall or the router, but is normally best placed on the device most at network edge. A similar rule could be applied to software firewalls installed on a workstation as well, such as the built-in firewall on Windows or Mac OS X.
For help with creating firewall rules on a Barracuda CloudGen Firewall, see Firewall Access Rules. For the Barracuda NextGen Firewall, see Firewall Rules. If you are not using a Barracuda firewall solution, note that each firewall or router has a unique configuration interface and these vary greatly. If you are uncertain, you should check your router or firewall documentation or contact the manufacturer to see if this is possible with your device.