a month ago
Dear everyone
I am experiencing an issue with DNS provisioning for a custom domain on my Railway project.
Background:
I initially deployed this project on Railway Trial plan
When the trial expired, the old project and its deployments were automatically deleted
I recently upgraded to Hobby plan and recreated/redeployed the same project from GitHub
The new project is: Dhamma-AI-Network (freshly deployed)
Issue Details:
Project: Dhamma-AI-Network (new deployment after trial expiry)
Custom Domain: www.dhamma-ai.org
Current Status: "Waiting for DNS update" (has been pending for 24+ hours)
Domain Registrar: Z.com
What I've Done:
Added custom domain www.dhamma-ai.org in the new Railway project settings
Retrieved DNS records from Railway:
CNAME: www → yi2g2dwdg.up.railway.app
TXT: _railway-verify → [verification value]
Updated DNS records at Z.com registrar to match exactly
Waited 24+ hours for DNS propagation
Current Situation:
Railway UI shows domain as "ACTIVE" with deployment successful
However, the domain still shows "Waiting for DNS update"
DNS resolution test shows records are updated at registrar
The Railway temporary URL (dhamma-ai-network-production.up.railway.app) works fine
Question:
Could the domain issue be related to the trial project's deletion? Is there a stale domain record or cache on Railway's end that needs to be cleared? Why is the custom domain still showing "Waiting for DNS update" despite correct DNS configuration?
Thank you for your assistance.
Best regards,
Warawut
3 Replies
a month ago
Your CNAME record is pointing to the old Railway target from your previous trial project (yig2dwdg.up.railway.app) instead of the new one assigned to your current deployment. When you recreated the project, a new CNAME target was generated. Update the CNAME record at your registrar to the value shown in your service's Settings under Networking for that domain, and it should resolve once the change propagates.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
Your CNAME record is pointing to the old Railway target from your previous trial project (`yig2dwdg.up.railway.app`) instead of the new one assigned to your current deployment. When you recreated the project, a new CNAME target was generated. Update the CNAME record at your registrar to the value shown in your service's Settings under Networking for that domain, and it should resolve once the change propagates.
a month ago
yig2dwdg.up.railway.app is the new one and I already updated it at DNS. It's still not working.
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
To correct our earlier message, we should have included the specific target. Your CNAME currently resolves to yig2dwdg.up.railway.app, but the target assigned to your current service is d7ceapse.up.railway.app. Update the CNAME record at your registrar to d7ceapse.up.railway.app and the domain should begin working once the change propagates.
Status changed to Awaiting User Response sam-a • about 1 month 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