My custom domain ai-dashboard.covcorp.co returns HTTP 404 {"message":"Application not found"} over HTTPS, even though the certificate is valid, DNS is correct and propagated, and the app itself is healthy. The service's own Railway URL (covenant-ai-dashboard-production.up.railway.app) returns 200 and works fine — only the custom domain fails to route.

Details:

• Project: covenant-ai-dashboard (id 025079a6-984c-4687-a6fc-32dc7b9895e2), environment: production
• Service: covenant-ai-dashboard (id 93fbbaeb-944b-4488-93e3-a7d3cbdd8787)
• Custom domain id: 0ffc91fd-9ec1-45cd-b4c3-f59fb5c1f4c4; certificate status: VALID
• DNS: CNAME ai-dashboard.covcorp.co → 8lqfjtr3.up.railway.app, fully propagated (Google 8.8.8.8 and Cloudflare 1.1.1.1 confirm); Railway shows current == required
• The edge target 8lqfjtr3.up.railway.app also returns the same 404 directly
• A prior custom-domain endpoint (uipkoika.up.railway.app) had the identical 404. I removed and re-added the domain, which produced a new endpoint — same behavior.
• I've tried: redeploying the service (succeeded), re-issuing the certificate (cert is VALID), and confirming there's a single clean custom-domain record. None resolved it.

The edge is not routing the custom domain to the deployment despite a valid cert, correct/propagated DNS, and a healthy app. This appears to be an edge/routing issue on Railway's side. Please help route the custom domain to the deployment.