a month ago
I purchased a domain for my service directly through Railway last weekend, and the Railway interface indicated that Railway would handle the DNS setup automatically.
The domain has been stuck at “Waiting for DNS to propagate” since Saturday, June 6, 2026. It is now Thursday, June 11, so this has been several days and appears to be beyond the normal DNS propagation window.
Because this was purchased and managed inside Railway, I do not believe this is a case where I manually misconfigured external DNS records. Could someone please check whether the Railway-managed DNS setup, verification, or certificate provisioning is stuck?
Please let me know whether this requires a manual re-verification, DNS repair, certificate retry, or a refund/reissue if the domain setup did not complete correctly.
4 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 26 days ago
23 days ago
puzzlegridworks.app, which I've purchased from Railway. Currently, when I attempt to access it, it says the connection is not private, and when I look at the domain under my deployed service, it still shows a state of "Waiting for DNS to propagate".
23 days ago
The same is occurring to me. Showing issue as the current config is different, but I have added the correct one in the DNS record in the Domain configuration. Note, but mine is a Custom Domain
1daydeveloper
The same is occurring to me. Showing issue as the current config is different, but I have added the correct one in the DNS record in the Domain configuration. Note, but mine is a Custom Domain
22 days ago
Please create your own thread.