Hi Railway team,

A custom domain on my project won't bind to its service despite Cloudflare DNS being correctly configured for >12 hours. The auto-generated *.up.railway.app domain works perfectly — only the custom domain is broken.

Project ID: 05f09ab9-2d91-4e1d-8993-1ebc404efd50 Project name: topscore Service: topscore (web service, NOT the Postgres service) Custom domain attempting to bind: topscore-api.halegroup.ai Working auto-generated URL: https://topscore-production.up.railway.app

Steps taken:

1. Added topscore-api.halegroup.ai via the dashboard (Settings → Networking → Custom Domain). Railway gave me CNAME target hw62r8nj.up.railway.app.
2. Set a CNAME record on Cloudflare DNS for topscore-api pointing at that target, proxy disabled (gray cloud).
3. After ~30 minutes still showing "Waiting for DNS update", I deleted and re-added the custom domain. New CNAME target was wv5nst43.up.railway.app. Updated Cloudflare to match.
4. Public DNS now resolves correctly: $ dig @1.1.1.1 topscore-api.halegroup.ai topscore-api.halegroup.ai. 300 IN CNAME wv5nst43.up.railway.app. wv5nst43.up.railway.app. 60 IN A 66.33.22.63
5. Despite this, the dashboard still shows "Waiting for DNS update" >12 hours later, and curl returns Railway's edge 404: $ curl -k https://topscore-api.halegroup.ai/health {"status":"error","code":404,"message":"Application not found","request_id":"..."}
6. Same request to the auto-generated URL works perfectly: $ curl https://topscore-production.up.railway.app/health {"ok":true,"ts":1778314615498}

So the service is healthy, DNS is correct on Cloudflare, but the edge proxy never associated the hostname with the service. Could someone check what's holding up the binding? Happy to provide additional info, project access, or run diagnostics.

Thanks, Daniel Hale