Plan: Hobby | Project: observant-gratitude (fb16ea07-ef53-4a79-88d9-2c4b122706e8) | Service: alarkon-crm-web (510a52b6-be2f-41e1-8bfd-aba168716c6c)

Custom domain www.alarkoncrm.com returns 404 with x-railway-fallback:true, even though everything is correct:

• Service works on its Railway domain: https://alarkon-crm-web-production.up.railway.app → 200
• Deploy logs: [express] serving on port 5000
• Custom domain shows Online, SSL cert = VALID
• DNS propagated: www.alarkoncrm.com CNAME wqxmglye.up.railway.app
• Only 1 custom domain on service (Hobby allows 2)

KEY: *** working Railway domain WITH the custom Host also 404s:

curl -H "Host: www.alarkoncrm.com" https://alarkon-crm-web-production.up.railway.app → 404 (x-railway-fallback)

curl https://alarkon-crm-web-production.up.railway.app → 200

App is healthy; the edge is not routing the custom Host. Likely orphaned/stale custom-domain records from repeated delete+recreate cycles.

Already tried: delete+recreate, redeploy, restart, targetPort change, manual cert issue (→VALID), brand-new clean service, deleted old service. Still fallback 404 after a full night.

Please release any orphaned custom-domain records for alarkoncrm.com / www.alarkoncrm.com and re-sync the edge routing to service alarkon-crm-web. I can add _railway.verify TXT records to prove ownership if needed.