18 days ago
Domain: dsl.arts.columbia.edu
The custom domain has been stuck on “Waiting for DNS update” since September 9.
Both required DNS records are publicly resolving correctly:
CNAME
dsl.arts.columbia.edu → r3tt01vm.up.railway.app
TXT
_railway-verify.dsl.arts.columbia.edu
railway-verify=ca168915217a26d1a86008cb32865b23306d720d95a0cc7c4da19e55a6397fbd
Running dig returns both records successfully, but Railway still shows the TXT verification record as pending.
The domain is configured to target port 3000.
The DNS records were added by Columbia IT on September 9, 2026. They have been in place for eight days. I verified on September 17 that both the CNAME and TXT records are publicly resolving correctly using dig.
How can i resolve this issue?
1 Replies
Status changed to Awaiting Railway Response Railway • 18 days ago
18 days ago
Your DNS records are both correctly configured and the TXT verification token matches. The verification status did not update after your DNS records propagated, which left the certificate stuck. A re-issuance has been started and may take a few minutes to complete.
Status changed to Awaiting User Response brody • 18 days ago
11 days 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 • 11 days ago