Investigating the DNS_PROBE_POSSIBLE Error When Accessing Okta Applications

An error occurs when an end user attempts to access an application protected by Okta from the End-User Dashboard by selecting the application tile. This issue stems from local network Domain Name System (DNS) misconfigurations or a stale browser cache. Clearing the browser cache, flushing the local DNS cache, and verifying network DNS settings resolve this issue.

DNS_PROBE_POSSIBLE

Review the error message displayed in the browser when the application fails to load.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Custom application access
• DNS_PROBE_POSSIBLE error

The web browser is unable to translate the application domain URL into a numeric IP address. This typically stems from local network DNS misconfigurations or a stale browser cache.

How is the DNS_PROBE_POSSIBLE error resolved?

Verify the browser DNS resolution, flush the local DNS cache, verify network DNS settings, and review security settings by following these troubleshooting steps.

1. Open a new tab in the Google Chrome browser and navigate to chrome://net-internals/#dns.
   Review the DNS lookup page to verify the browser DNS resolution.
    
2. Enter the domain name in the Domain field, and then select Lookup to check whether the browser can resolve the IP address.
3. Select Clear host cache to purge local DNS entries within the browser.
4. Flush the operating system DNS cache via the terminal.
5. Clear the browser cookies and cached web data.
6. Test network resolution using a public DNS provider, such as Google Public DNS at 8.8.8.8.
7. Audit browser extensions, VPNs, or proxy settings that might interfere with DNS routing.