2 months ago
My custom domain pay.zallandsons.com has been stuck on "Waiting for DNS update" for over 8 hours despite DNS being fully propagated globally.
Details:
• Service: zall-portal
• Domain: pay.zallandsons.com
• CNAME record: pay → 7458tyxv.up.railway.app ✓ (verified)
• TXT verification record: _railway.pay → (verification record set) ✓ (verified)
• DNS propagation: Confirmed globally on dnschecker.org
What I've tried:
• Verified DNS records are correct and globally propagated
• Re-added the domain to the service to force detection refresh
• Waited 8+ hours
Request: Please manually trigger SSL certificate provisioning for this domain. The DNS is correct on my end—this appears to be a backend detection issue.
Thanks,
Greg
2 Replies
2 months ago
Hi, what is your DNS provider? Make sure it's one that supports adding a CNAME on the apex (root), Cloudflare is a very good one
pay.zallandsons.com is a subdomain, not the apex — the CNAME record for pay pointing to 7458tyxv.up.railway.app is correctly set in Namecheap and has been globally propagated for over 24 hours (verified on dnschecker.org). The TXT verification record _railway.pay is also set. The issue appears to be that Railway is not detecting the DNS and provisioning the SSL cert on your end. Can you manually trigger SSL provisioning for this domain?