Also i've seen waaay too many failures from UTM dns in regard to the http proxy. This causes mis categorizations of sites.
If you really want to use a public dns I would highly suggest using hte dns routing feature to have the utm route internal dns to the internal dns server not itself..that way all external traffic will go outside and the internal traffic will get properly resolved by the internal dns server.
I've not seen this, William. Do you have an example that I can reproduce?
Yes, this is item 4 in that post, using Request Routing to have internal FQDNs resolved.
Cheers - Bob
Owner: Emmanuel Technology Consulting
Former Sophos SG(Astaro) advocate/researcher/Silver Partner
PfSense w/Suricata, ntopng,
Other addons to follow
Owner: Emmanuel Technology Consulting
Former Sophos SG(Astaro) advocate/researcher/Silver Partner
PfSense w/Suricata, ntopng,
Other addons to follow
Owner: Emmanuel Technology Consulting
Former Sophos SG(Astaro) advocate/researcher/Silver Partner
PfSense w/Suricata, ntopng,
Other addons to follow
CTO, Convergent Information Security Solutions, LLC
https://www.convergesecurity.com
Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
I'll just say this and leave it where it lays; never in 10 years of reselling Astaro ASG / Sophos UTM have I had a problem configuring it as Bob describes (and apparently as I described it to him, that must've been ages ago [:)] ) to do it. I'm not an advocate of using the UTM's DNS Proxy as your sole DNS (except for remote networks as a backup DNS resolver if a VPN to internal networks goes down, etc.) -- if you are on a Microsoft AD network, then, certainly, you have your clients and internal servers point at your DC(s) for DNS... but I have those servers point at the UTM for external (Internet) DNS name resolution, and I point the UTM at either the ISP's DNS (depends on how well the ISP maintains their DNS services) or OpenDNS, etc. Again, never had an issue.
To each his own, not saying my way is necessarily the "right" way, but it does simplify troubleshooting some issues, and further isolates the internal network from the big bad Internet, and has certainly served me well over the past 10 years or so. In this case, I think the issue the OP was having was because they had DNSSEC enabled, and were using OpenDNS ... that won't work.
2014:05:11-00:36:22 utm selfmonng[3772]: W actionCmd(-): '/var/mdw/scripts/cssd restart'
2014:05:11-00:36:23 utm selfmonng[3699]: I check Failed increment named_running counter 1 - 3
2014:05:11-00:36:23 utm selfmonng[3699]: W check Failed increment cssd_running counter 3 - 3
2014:05:11-00:36:23 utm selfmonng[3699]: W triggerAction: 'cmd'
2014:05:11-00:36:23 utm selfmonng[3699]: W actionCmd(-): '/var/mdw/scripts/cssd restart'
2014:05:11-00:36:27 utm selfmonng[3772]: W check Failed increment named_running counter 3 - 3
2014:05:11-00:36:27 utm selfmonng[3772]: W NOTIFYEVENT Name=named_running Level=INFO Id=119 suppressed
2014:05:11-00:36:27 utm selfmonng[3772]: W triggerAction: 'cmd'
2014:05:11-00:36:27 utm selfmonng[3772]: W actionCmd(+): '/var/mdw/scripts/named restart'
2014:05:11-00:36:28 utm selfmonng[3699]: I check Failed increment cssd_running counter 1 - 3
2014:05:11-00:36:29 utm selfmonng[3772]: W child returned status: exit='1' signal='0'
2014:05:11-00:36:29 utm selfmonng[3772]: I check Failed increment cssd_running counter 1 - 3
2014:05:11-00:36:33 utm selfmonng[3699]: I check Failed increment named_running counter 2 - 3
2014:05:11-00:36:33 utm selfmonng[3699]: I check Failed increment cssd_running counter 2 - 3
2014:05:11-00:36:34 utm selfmonng[3772]: I check Failed increment named_running counter 1 - 3
2014:05:11-00:36:34 utm selfmonng[3772]: I check Failed increment cssd_running counter 2 - 3
2014:05:11-00:36:35 utm selfmonng[3772]: I check Failed increment smtp_running counter 1 - 15
2014:05:11-00:36:38 utm selfmonng[3699]: W check Failed increment named_running counter 3 - 3
2014:05:11-00:36:38 utm selfmonng[3699]: W NOTIFYEVENT Name=named_running Level=INFO Id=119 suppressed
2014:05:11-00:36:38 utm selfmonng[3699]: W triggerAction: 'cmd'
2014:05:11-00:36:38 utm selfmonng[3699]: W actionCmd(+): '/var/mdw/scripts/named restart'
2014:05:11-00:36:39 utm selfmonng[3772]: W check Failed increment cssd_running counter 3 - 3
2014:05:11-00:36:39 utm selfmonng[3772]: W triggerAction: 'cmd'