Hi!
We have 50x Mac/Win users in our office, accessing an internal wiki. Remote users connect to the UTM via OpenVPN client.
Internal wiki: wiki.example.com (10.2.2.20)
When VPN clients or internal clients try to reach the wiki, half the time they are reaching an external internet site that exists with the same ip address as our internal one. Therefore, sometimes the clients are using the public DNS Servers first, instead of the UTM which is configured as the primary DNS Server.
Our Sophos support company recommend configuring DHCP on the UTM to give clients only one DNS Server - the UTM.
Unfortunately, in practise, this really slows down internet browsing for clients, especially for VPN clients, understandably.
I found the DNS Best Practise guide here, but it talks about an internal DNS server:
https://community.sophos.com/products/unified-threat-management/f/management-networking-logging-and-reporting/32566/solved-dns-best-practice#pi2353=2
We don't have an internal DNS Server, only the UTM itself, which is our Firewall, DHCP Server, VPN Server and Threat Management solution.
- Does this guide still apply to me?
- Is the UTM acting as an actual DNS Server, or just a forwarder of some kind?
- Would we be better served with a dedicated internal DNS Server running on a linux VM, for example? I want to keep our infrastructure as compact as possible.
Thanks for any help or suggestions!
This thread was automatically locked due to age.
