Your CNAME record is pointing to an old Railway target that no longer exists for this domain entry. When you removed and re-added the domain, a new CNAME target was generated, but your DNS provider still has the previous one. The TXT verification record is correct, but verification cannot complete until the CNAME matches. Update the CNAME at your DNS provider to the target currently shown in your service's Settings under Networking, and it will stay stable as long as the domain entry is left in place.

Thanks for the info! I've updated the CNAME record at my DNS provider to the new target value shown in my service's Networking settings, and I've verified it's propagating correctly:

dig crearestudio.co CNAME +short @8.8.8.8

→ fmq2b3zp.up.railway.app.

It's been several hours since the update and the domain is still showing "Waiting for DNS update" in the dashboard. Could you please check if there's still an issue on your end, or manually trigger the verification?

Thanks again!

Your CNAME is now correct and propagated. The remaining blocker is the TXT verification record: it is currently published on the root domain itself (@), but Railway expects it on the _railway-verify subdomain. At your DNS provider, create a TXT record with the name/host set to _railway-verify (not @ or blank) using the same verification value shown in your service's Networking settings. Verification and certificate issuance will resume automatically once the corrected record propagates.