2 months ago
"Custom domain app.eatoc.co.uk is stuck on 'Waiting for DNS update' for the TXT record despite correct records in place for several days. CNAME (app → z7srxzq7.up.railway.app) shows green. TXT (_railway.app → railway-verify=ab5227f11a7bad37beb2e99ccafd94e2c48acab5e76f9c8cae671655265c94d3) has been correctly set in GoDaddy for 3+ days, TTL 1 hour. Domain has been deleted and re-added 3+ times. Please manually verify or reset the domain verification on your end. Service: etoc-crm, project: authentic-recreation."
Pinned Solution
2 months ago
I'd try re-adding the TXT record. I ran nslookup and it returned NXDOMAIN.
3 Replies
2 months ago
Your CNAME record is propagated correctly, but the TXT verification record is not resolving at the expected hostname. Our system expects the TXT record at _railway-verify.app.eatoc.co.uk (host name _railway-verify.app in GoDaddy), and a public DNS lookup for that hostname returns no records. The certificate is stuck in ownership validation because of this. In GoDaddy, make sure the TXT record's "Name" or "Host" field is set to exactly _railway-verify.app with the verification token as the value, then allow a few minutes for propagation.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
The alteration has been made an hour ago with no change? screen shot provided
Attachments
Status changed to Awaiting Railway Response Railway • about 2 months ago
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 • about 2 months ago
2 months ago
I'd try re-adding the TXT record. I ran nslookup and it returned NXDOMAIN.
Status changed to Solved 0x5b62656e5d • about 1 month ago