19 days ago
"web" service custom domain (app.caizerquip.com) stuck on "Waiting for DNS update" for 5+ days. Browser still gets the default *.up.railway.app cert.
Verified via dnschecker.org/nslookup: CNAME and TXT (_railway-verify) both correctly set and fully propagated. No CAA record. DNSSEC disabled.
Tried: re-adding the domain multiple times with fresh CNAME/TXT each time, two different subdomain names on the same service (same failure both times), service restart, waiting 24+ hrs each time.
Note: a different service in the same project got a custom domain working on the first try, same root domain — so this seems specific to the "web" service's cert issuance, not DNS.
Could someone check cert issuance logs for the "web" service?
6 Replies
Status changed to Awaiting Railway Response Railway • 19 days ago
Status changed to Open brody • 19 days ago
0x5b62656e5d
Your TXT record is malformed. It should start with `railway-verify=`.
19 days ago
Just the hash string alone worked fine for the other service — no issues. It was actually adding the "railway-verify=" prefix that caused a problem. So I don't think this is the issue.
19 days ago
Have you tried putting the exact string Railway provided into your DNS service instead of modifying it?
0x5b62656e5d
Have you tried putting the exact string Railway provided into your DNS service instead of modifying it?
18 days ago
Initially, I entered the CNAME exactly as provided, but it didn't work, so I tried changing it. Then I tested another CNAME by entering only the value (without the full hostname), and surprisingly, that one worked. That's why I tried doing the same with this record as well.
18 days ago
sorry, that was TXT not CNAME
Status changed to Solved 0x5b62656e5d • 17 days ago