Thread Info
  • Locked Locked
  • Replies 4 replies
  • Subscribers 2 subscribers
  • Views 16247 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

UTM Home DNS problems

JonathanGriggs

Ok, I'm new to Sophos UTM, downloaded the Home version recently and wanted to give it a try.  I only have a few devices behind the UTM box, one being a Synology NAS.  Synology offers a service call QuickConnect that connects through http connections, supposedly not requiring any ports being opened.  Anyway, the Synology QuickConnect service does not work behind the UTM, and I believe it's a DNS issue.  I don't understand DNS very well, I usually use public DNS servers (8.8.8.8, 8.8.4.4, 208.67.222.222, etc) and things work.  However, as I read Sophos' DNS Best Practice post, it indicates there's an internal DNS server separate from the UTM.  Am I reading this right, am i supposed to have an internal DNS server setup on a device other than the UTM?  Anyway, I followed the Best Practice guidelines through point 3 where I entered the reverse DNS lookup entry under Request Routing, and my Synology still doesn't work.  I'm fairly certain there's a DNS error, but I can't figure it out.  Other computers behind the UTM are pointed to the UTM as the DNS and are able to resolve names.  Any ideas (the helpful kind, please)?



This thread was automatically locked due to age.
Parents
  • I doubt this being a DNS issue. What have you set up as DNS server in your Synology?

    Have you checked the firewall, IPS and webfilter logs?
    I bet there is something blocked that's listed in one of these logs...

    Btw: there is no problem in using UTM as internal DNS server for home setups. No need for a separate internal DNS server. Also no need for a request routing, when you don't have an internal DNS server.

    ----------
    Sophos user, admin and reseller.
    Private Setup:

    • XG: HPE DL20 Gen9 (Core i3-7300, 8GB RAM, 120GB SSD) | XG 18.0 (Home License) with: Web Protection, Site-to-Site-VPN (IPSec, RED-Tunnel), Remote Access (SSL, HTML5)
    • UTM: 2 vCPUs, 2GB RAM, 50GB vHDD, 2 vNICs on vServer (KVM) | UTM 9.7 (Home License) with: Email Protection, Webserver Protection, RED-Tunnel (server)
Reply
  • I doubt this being a DNS issue. What have you set up as DNS server in your Synology?

    Have you checked the firewall, IPS and webfilter logs?
    I bet there is something blocked that's listed in one of these logs...

    Btw: there is no problem in using UTM as internal DNS server for home setups. No need for a separate internal DNS server. Also no need for a request routing, when you don't have an internal DNS server.

    ----------
    Sophos user, admin and reseller.
    Private Setup:

    • XG: HPE DL20 Gen9 (Core i3-7300, 8GB RAM, 120GB SSD) | XG 18.0 (Home License) with: Web Protection, Site-to-Site-VPN (IPSec, RED-Tunnel), Remote Access (SSL, HTML5)
    • UTM: 2 vCPUs, 2GB RAM, 50GB vHDD, 2 vNICs on vServer (KVM) | UTM 9.7 (Home License) with: Email Protection, Webserver Protection, RED-Tunnel (server)
Children
  • in reply to scorpionking
    Hey all,

    Just as a follow-up here I am having a DNS issue that the OP might have been experiencing.

    Having setup DNS as per the guides I am resolving DNS only to external sites. I seem to have no internal DNS resolution. I have the UTM as my DHCP server and am expecting the UTM to resolve DNS on my internal network. Have I missed a setting somewhere?

    Thanks,

    James
Unfiltered HTML