06-25-2026 06:31 AM
The private application hosted on AWS behind an Application Load Balancer (ALB), and the ZTNA Connector is also deployed within the AWS environment.
We configured the application FQDN in the ZTNA Connector however, the application status remains in a DOWN state. To address potential DNS resolution issues, we added the internal DNS servers ip in Prisma Access, but the application status is still showing as DOWN.
As part of our troubleshooting, we configured the application's IP address in the ZTNA Connector and verified that the application is accessible using the IP address. However, access via the FQDN is not working.
For further validation, we configured the ALB FQDN in the ZTNA Connector and confirmed that it is reachable. The ALB FQDN shows an UP status, and connectivity tests from the ZTNA Connector to the ALB are successful.
also validated that the Internal DNS IP also able Ping from the connector, but the application not getting up & reachble using the FQDN.
Despite this, the application FQDN continues to show a DOWN status in ZTNA and remains inaccessible.
Please provide guidance on potential causes and resolutions for this issue?
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
