Stopping Open DNS - FireBrick 105: Difference between revisions

From AAISP Support Site
No edit summary
No edit summary
Line 2: Line 2:


=FireBrick 105:=
=FireBrick 105:=

[[File:FireBrick-icons.png]]

'''In a factory state the Fillters on a FireBrick 105 will not allow DNS to the FireBrick from the WAN - the default state is to block incoming traffic, but to allow outgoing traffic.
'''In a factory state the Fillters on a FireBrick 105 will not allow DNS to the FireBrick from the WAN - the default state is to block incoming traffic, but to allow outgoing traffic.
'''
'''

Revision as of 14:48, 18 June 2013

105-small.gif

FireBrick 105:

FireBrick-icons.png

In a factory state the Fillters on a FireBrick 105 will not allow DNS to the FireBrick from the WAN - the default state is to block incoming traffic, but to allow outgoing traffic. However, in some cases, customers disable the firewall by adding a rule that allows all traffic in. In this case, a new rule is needed to block DNS to the FireBrick.

Create a Firewall filter to block port 53, from the WAN to the FireBrick, and make sure it's before any other rule that may allow this traffic in:


Name: BlockOpenDNS
Source: WAN
Target: FireBrick (The name of your FireBrick)
Action: Drop
Target ports: 53
Protocol: UDP

FireBrick-OpenDNS-Rule.png