6 hours ago
Custom domain stuck on "Waiting for DNS update" for 24+ hours
Domain: kudzuarts.com
Project: energetic-vibrancy · Service: kudzu · Environment: production
The domain has been attached to the service (target port 8080) for over 24 hours and still shows "Waiting for DNS update." No certificate has been issued, and the domain does not serve over HTTP or HTTPS.
DNS is correct and globally propagated — verified on dnschecker.org from Google, Quad9, OpenDNS, Cloudflare, Akamai and others:
_railway-verify.kudzuarts.com TXT = railway-verify=593c733e5f3fe2dfcf31bba69
Apex record points to the target Railway issued (xw2mwhhq.up.railway.app)
I have removed and re-added the domain once, updating the DNS record to the new target each time. The service itself is healthy and serves correctly at kudzu-production.up.railway.app.
1 Replies
6 hours ago
Your CNAME record is correct and propagated, but the TXT verification record at _railway-verify.kudzuarts.com is truncated. It currently ends at ...bba69, but the full value is significantly longer. You can find the complete verification value on the custom domain settings page for your service. Update the TXT record at your registrar with the full string, and once it propagates, verification and certificate issuance will proceed. You can reply here once updated so we can confirm it picked up correctly.
Status changed to Awaiting User Response Railway • about 6 hours ago