Comments
-
james - I may have found the issue. Some genius, before my time, assigned the Corporate network IP range 192.168.1.0/24. Long term solution would be to migrate to a new local network range 10.10.x.x. Evaluating short term solutions to this issue.
-
Awesome!!
-
Thanks perfect. I have a block of 5 static IPs - (1.2.3.4 - 1.2.3.8) SMTP email is going out on the Ip ending in 4. How do I create a rule that will direct email to go out using the IP ending in 5 instead of 4?
-
like this ?
-
Bruce need your opinion on the following rule I saw in another post. How about a packet filter policy to DENY DNS from any trusted. Then create another rule from ANY trusted to only allow my DNS Server outside DNS Servers since we are in an Active Directory environment?
-
In reality I may not need the DNS policy - 2nd one on the list. Just DNS-Proxy.
-
I'm going to enable logging on DNS-Proxy and upgrade backup to Fireware 12.5.9 Update 1 to see what's being DENIED, as nothing is being allowed once I'm back on 12.5.9. I do not have DNSWatch Enabled but thinking of enabling it moving forward. Had to downgrade because we can't be without internet for extended amount of…
-
I currently have 2 DNS Policies, DNS and DNS-proxy. See attached. But I do not have DNS Watch enabled.
-
We have Active Directory Domain, my primary and secondary DNS servers are set to resolve Open DNS. Do I have to setup DNS in the newest fireware?
-
I'm conviced Dimension is the way to go, currently running Log Server, but we do not run VM. Here comes the dumb question, Does dimension runs on Windows Server?