a month ago
I moved a simple React webpage running in a Docker container (which runs just fine on my Raspi 5) to Railway and added a custom domain I own.
I published the correct DNS records and verifyied they are visible on DNSchecker.org. They are exactly he same as the ones on another webpage I already have successfully published on Railway before.
However, I am waiting for about 6 hours for the page to appear. Railway shows "Waiting for DNS update".
Is that normal?
3 Replies
a month ago
yes, this can be normal.
Railway doesn’t just check if the DNS record exists — it waits until their own DNS resolvers see it pointing to the right place. Even if DNSChecker is all green and your provider looks correct, Railway may still be seeing cached/old data.
The most common reasons:
High TTL (1h, 4h, 24h) from previous records → some resolvers keep the old value longer
Wrong record type (CNAME vs A / ALIAS, especially for root domains)
DNSChecker ≠ Railway’s resolvers — they don’t always update at the same time
6 hours is annoying, but still within a normal propagation window.
What I’d check:
Hostname matches exactly (no missing
www)Record type matches what Railway shows
TTL is ≤ 300s (if possible)
Avoid deleting/re-adding the domain — that usually resets the wait
If it’s still stuck after ~24h, then it’s worth opening a support thread.
If you want, tell me whether this is a root domain or subdomain and which DNS provider you’re using — happy to take a look.
gabztoo
yes, this can be normal.Railway doesn’t just check if the DNS record exists — it waits until their own DNS resolvers see it pointing to the right place. Even if DNSChecker is all green and your provider looks correct, Railway may still be seeing cached/old data.The most common reasons:High TTL (1h, 4h, 24h) from previous records → some resolvers keep the old value longerWrong record type (CNAME vs A / ALIAS, especially for root domains)DNSChecker ≠ Railway’s resolvers — they don’t always update at the same time6 hours is annoying, but still within a normal propagation window.What I’d check:Hostname matches exactly (no missing www)Record type matches what Railway showsTTL is ≤ 300s (if possible)Avoid deleting/re-adding the domain — that usually resets the waitIf it’s still stuck after ~24h, then it’s worth opening a support thread.If you want, tell me whether this is a root domain or subdomain and which DNS provider you’re using — happy to take a look.
a month ago
Thanks! It was just the missing "www"! :-)
After I added it, the webpage was available within a minute.
marvinbo
Thanks! It was just the missing "www"! :-)After I added it, the webpage was available within a minute.
a month ago
No problem! Just send a message if you need anything else. Approving the response would be a great help. 
Status changed to Solved brody • about 1 month ago