2 months ago
My custom domains are stuck on "Waiting for DNS update" even after correct DNS setup.
Details:
- app.abc.com → resolves correctly to Railway domain
- api.abc.com → resolves correctly
- TXT verification records are also resolving correctly
nslookup confirms both CNAME and TXT are working.
Default Railway domains are working fine.
Looks like DNS verification is stuck/cached on Railway side.
Can you manually re-trigger verification or check this?
8 Replies
2 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 2 months ago
2 months ago
If Railway doesn't automatically detect the updates within the hour, try removing your domains from Railway and the associated records from your DNS provider, wait for ~10-15 mins, then re-add them back.
0x5b62656e5d
If Railway doesn't automatically detect the updates within the hour, try removing your domains from Railway and the associated records from your DNS provider, wait for \~10-15 mins, then re-add them back.
2 months ago
i removed and updated again after 20 minutes but now nothing happening
0x5b62656e5d
If Railway doesn't automatically detect the updates within the hour, try removing your domains from Railway and the associated records from your DNS provider, wait for \~10-15 mins, then re-add them back.
2 months ago
still same issue
8 days ago
Anyone found a fix for this? having the same issue
8 days ago
Hey, ran into the exact same issue — domains stuck on "Waiting for DNS update" even though nslookup confirmed both CNAME and TXT were resolving correctly.
What worked for me: I updated the CNAME and TXT records in Hostinger (where my domain's DNS is managed). After waiting about 30–40 minutes, Railway picked up the change and the status updated correctly on its own — no need to remove/re-add the domain.
If you're stuck, double check your records are correct in Hostinger and then just give it a bit more time than you'd expect. Hope this saves someone the troubleshooting!
danish-anwar
still same
8 days ago
The problem happened because the main domain was already mapped to another service in Railway. Because of that, the subdomain could not be mapped properly.
I fixed it by moving the main domain to another hosting provider and keeping only the subdomain connected to Railway.