Facing issue in application access & health status shows as down in Prisma ZTNA Connector.

[P.Sawant533098]

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?

[nikoolayy1]

Why you want to reach the APP directly and through ALB as you confirmed it works that way with FQDN or IP?

Also did you check security groups/acl in AWS if they are blocking traffic? 

You may use AWS flow logs Logging IP traffic using VPC Flow Logs - Amazon Virtual Private Cloud if needed.

ZTNA connector ZTNA Connector Diagnostic Tools has nslookup and if that works then it is not DNS and if not then try tcp ping on the app port to see if security or routing issues are the ones responsible.