Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 5 subscribers
  • Views 6707 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

Access to externally hosted website blocked by UTM

MikeTaylor

Everything was working fine until the most recent update to our UTM (it's now using firmware version 9.404-5) Now when I try to browse the company website from any internal device whether connecting through the proxy or not I get this page cannot be found messages. When I connect using a remote device it works fine. The website ip address has not changed and nothing has changed on the internal network. I have set the various profiles to allow access to the domain and all sub domains. Where can I set a bypass for the corporate website?

The website I am trying to connect to is http://www.falklandhouseschool.org and it's ip address is 54.154.135.21



This thread was automatically locked due to age.
Parents
  • 0

    Hi, Mike, and welcome to the UTM Community!

    If you're using the Proxy in Standard mode, then it's the Proxy that initiates the DNS request. In Transparent mode, it's the client that makes the request, so it's confusing that you say you're not in Transparent, but changing the DNS configuration on the client corrects the behavior.  How does your setup compare to DNS Best Practice?

    It's not common that an upgrade "breaks" a configuration, but it does happen.  What happens if you restore the configuration backup from just before the Up2Date was applied?

    Cheers - Bob

Reply
  • 0

    Hi, Mike, and welcome to the UTM Community!

    If you're using the Proxy in Standard mode, then it's the Proxy that initiates the DNS request. In Transparent mode, it's the client that makes the request, so it's confusing that you say you're not in Transparent, but changing the DNS configuration on the client corrects the behavior.  How does your setup compare to DNS Best Practice?

    It's not common that an upgrade "breaks" a configuration, but it does happen.  What happens if you restore the configuration backup from just before the Up2Date was applied?

    Cheers - Bob

Children
No Data