a month ago
I'm having issues with a custom domain binding on my project.
Project: vivacious-fascination (ID: 44de6abb-00b8-4f83-97d9-2f10bb46961a)
Custom domain: www.medilifepraxis.ch
Issue: The custom domain is registered in Railway and DNS is correctly set (CNAME www -> xu3yml6y.up.railway.app, and _railway-verify to railway-verify=xxxxxxxxx). However, when I access www.medilifepraxis.ch, Railway's edge returns "medilifepraxis.ch refused to connect."
Could you please help verify why the custom domain isn't being bound to the service?
Pinned Solution
a month ago
You're trying to add your custom domain as www but you're adding the TXT record to @.
As mentioned above, the TXT record needs to be on the same hostname as your CNAME record.
4 Replies
Status changed to Open Railway • about 1 month ago
a month ago
You need to put the TXT record on _railway-verify.www, not _railway-verify.
0x5b62656e5d
You need to put the TXT record on `_railway-verify.www`, not `_railway-verify`.
a month ago
No, this doesn't work. Also AI Agent is telling me that is not correct. Anyway, when I do nslookup -type=TXT _railway-verify.medilifepraxis.chns.hostpoint.ch I got my verify string, so this should not be the issue.
a month ago
You're trying to add your custom domain as www but you're adding the TXT record to @.
As mentioned above, the TXT record needs to be on the same hostname as your CNAME record.
0x5b62656e5d
You're trying to add your custom domain as `www` but you're adding the TXT record to `@`. As mentioned above, the TXT record needs to be on the same hostname as your CNAME record.
a month ago
Ok, I agree, issue was in this area. I defined my side as "medilifepraxis.ch" instead of "www.medilifepraxis.ch", this changed the way TXT is configured, it is with _railway-verify.www.
Status changed to Solved Railway • about 1 month ago