2 months ago
My custom domain won't activate even though DNS is verified correct globally. Been stuck 14+ hours.
Setup:
- Project/environment: peaceful-appreciation / production
- Service: shb-platform (serves shb-platform-production.up.railway.app, which returns HTTP 200 — app is healthy)
- Custom domain added to this service, port 8080
- Railway's expected CNAME target: 26pntslb.up.railway.app
DNS (verified correct):
- www.salonihariyani.com CNAME → 26pntslb.up.railway.app
- Confirmed identical on Google (8.8.8.8), Cloudflare (1.1.1.1), OpenDNS, and Quad9
- Single clean CNAME record, TTL 300, no duplicate/conflicting records, no A record on www
- Has been correct and fully propagated for 14+ hours
Problem:
- The domain row shows "Port 8080 · Waiting for DNS update" (yellow warning) and never verifies
- https://www.salonihariyani.com returns HTTP 404 with header x-railway-fallback: true
- It serves Railway's default *.up.railway.app cert (no cert issued for my domain)
- Sending Host: www.salonihariyani.com to my app's working edge returns 404 — the service doesn't recognize the hostname
Tried:
- Confirmed domain is on the correct service + production environment
- Removed and re-added the domain multiple times (each generates a new target, which I updated in DNS to match)
- No CAA records blocking cert issuance
The DNS is provably correct from every resolver, but Railway's edge returns x-railway-fallback for the hostname — so it seems the custom domain isn't attaching to my deployed service. What am I missing, or is this a platform issue? Thanks!
1 Replies
2 months ago
Custom domains require two DNS records: the CNAME (which you have) and a TXT record for ownership verification. Your CNAME is propagated correctly, but the TXT verification record is missing, which is why the domain stays on "Waiting for DNS update" and returns the fallback 404. Add a TXT record at the hostname shown in the domain's settings in your Railway dashboard with the verification value displayed there, then allow a few minutes for propagation and verification to complete.
Status changed to Awaiting User Response Railway • about 2 months ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago