Stopping Open DNS - FireBrick 105: Difference between revisions

← Older edit

Stopping Open DNS - FireBrick 105 (view source)

Revision as of 23:58, 17 August 2018

240 bytes added , 17 August 2018

→‎FireBrick 105: clean up

Reedy

editor

698

edits

Revision as of 10:09, 18 June 2013 (view source) AA-Andrew (talk \| contribs) (Created page with "=FireBrick 105:= 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 a...")		Latest revision as of 23:58, 17 August 2018 (view source) Reedy (talk \| contribs) (→‎FireBrick 105: clean up)
(12 intermediate revisions by one other user not shown)
[[File:105-small.gif]] =FireBrick 105:=▼ 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.▼ ▲=FireBrick 105:= [[File:FireBrick-icons.png]] ▲'''In a factory state the ~~Fillters~~Filters 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. ==Instructions== 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 Target ports: 53 Protocol: UDP *Then re-test from the Control Pages: https://clueless.aa.net.uk/dnsresolvers.cgi [[File:FireBrick-OpenDNS-Rule.png]] [[Category:FireBrick]] [[Category:Open DNS Resolvers]] [[Category:AA Routers]]