2 months ago
Hi,
I've been trying to attach the custom domain api.fit-pass.fr to my Railway service for several hours and it's stuck on "Waiting for DNS update" with no progress.
Here's what I've done and verified:
- CNAME
api→ pointing to the correct Railway value (updated each time after recreating the domain) - TXT
_railway→railway-verify=ece7e3cfdcf6beced78ea5591f7f04f4fffe2dd8cb2c3be5830008d0fa763452(full value, confirmed correct) - Both records are fully propagated globally (verified on dnschecker.org — all green)
- TTL reduced to minimum on both records
I've deleted and re-added the domain multiple times.
Each time Railway generates a new CNAME target, I update IONOS accordingly and confirm propagation — but Railway never moves past "Waiting for DNS update" and the TXT record keeps showing a warning icon.
This started during your EU-West latency incident earlier today (March 24). The incident is now resolved on your status page but the domain validation still isn't working.
Project: adequate-cat / Service: api / Domain: api.fit-pass.fr
Could you please check what's blocking the validation on your end?
Thanks in advance !
Cédric ROPTIN
FIT PASS
1 Replies
2 months ago
Your TXT verification record is on the wrong hostname. We expect the record at _railway-verify.api (resolving to _railway-verify.api.fit-pass.fr), but no TXT record exists there. It appears you created it at _railway instead of _railway-verify.api. Update the TXT host to _railway-verify.api with the value shown in your domain settings, and the verification should proceed.
Status changed to Awaiting User Response Railway • about 2 months ago
Status changed to Solved darryboutboul2 • about 2 months ago