16 days 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?
4 Replies
16 days 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 • 16 days ago
16 days 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.
16 days ago
i removed and updated again after 20 minutes but now nothing happening
https://api.zaydm.com/
https://app.zaydm.com/
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.
16 days ago
still same issue