Limitations of using FastHttps with Internal DNS Setup
  1. guides
  2. en
  3. Knowledge base
  4. Other troubleshooting
  5. Software and Solutions
  6. Limitations of using FastHttps with Internal DNS Setup

Limitations of using FastHttps with Internal DNS Setup

FastHttps Limitation for Internal Only DNS Setup

Issue description

When configuring the FastHttps Proxy in an environment where the internal DNS cannot resolve external targets, the connection will fail if the 'default' options are used.

Solution

To fix the issue, specify the host and port directly in your eSF application proxy configuration (e.g., www.myproxy.com:8043).
The 'default' setting currently uses the 'shouldProxy' method of the ProxyHelper API to check if the target is internal. This causes the process to attempt to resolve the address before connecting to the proxy server, which can lead to connection failures in some environments.
If this issue appears, please make sure to contact customer support for assistance in resolving this issue.