Application publish rule works by IP not FQDN

Scenario

External access to a published application succeeds with the public IP, but fails when users browse the normal hostname.

Recommended Resolution Path

1. Check public DNS, certificate binding, and virtual host or reverse proxy expectations.
2. Review whether the firewall is passing the correct host header to the backend.
3. Compare logs from the backend web service and the edge firewall during a failed request.
4. Fix the hostname path cleanly instead of teaching users to bypass with raw IP addresses.

Technician Notes

Document what changed, what confirmed the fix, and whether the issue points to a broader standards gap worth addressing for the client.