a month ago
Custom domain www.vyzit.co.in — CNAME verified successfully, but TXT record (_railway-verify) remains stuck showing unverified/yellow despite the DNS record being confirmed correct via direct dig query for many hours, matching exactly what's shown in the dashboard. Tried deleting and re-adding the domain — CNAME re-verified with a new value, but TXT verification remains stuck on the same unchanged value. No platform outage showing on status.railway.com. Can you check what's blocking TXT verification on your end? It's been 7 hrs plus with this issue now.
4 Replies
a month ago
The TXT verification record at the expected host is not resolving in public DNS at all, which is why verification has not completed. Additionally, the CNAME is currently pointing to an older Railway target rather than the one your dashboard now shows as required (this likely carried over from before you deleted and re-added the domain). You'll need to update both records at your registrar: set the CNAME to the current required value shown in your service's domain settings, and add a TXT record on the verification hostname with the full token value shown there, then allow time for propagation.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
The TXT verification record at the expected host is not resolving in public DNS at all, which is why verification has not completed. Additionally, the CNAME is currently pointing to an older Railway target rather than the one your dashboard now shows as required (this likely carried over from before you deleted and re-added the domain). You'll need to update both records at your registrar: set the CNAME to the current required value shown in your service's domain settings, and add a TXT record on the verification hostname with the full token value shown there, then allow time for propagation.
a month ago
"I've already verified both records directly via dig, independent of your dashboard, multiple times over many hours:
dig www.vyzit.co.in CNAME → returns spiy0ga3.up.railway.app (matches current dashboard value, and shows green in my dashboard)
dig _railway-verify.vyzit.co.in TXT → returns the exact value shown in my dashboard's TXT field, confirmed correct
Both records are provably live and correct in public DNS. This isn't a DNS propagation issue — something appears stuck on Railway's verification system specifically for the TXT check. Can this be escalated to a human engineer to check the verification service directly, rather than DNS propagation guidance?
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Update: the CNAME target value shown in my dashboard has now changed a third time (from t818won3, to spiy0ga3, to now 25zt8sw8.up.railway.app) without any action from me — yet it continues to show a green checkmark regardless of which value is current. This strongly suggests something is unstable in your verification/target-assignment system for this domain, not a DNS propagation issue on my end
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
The TXT verification token value is correct, but it is placed at the wrong hostname. Because the custom domain is on www, the verification record must live at _railway-verify.www.<your base domain>, not at _railway-verify.<your base domain>. Public DNS confirms the record exists only at the latter, which is why verification has not completed. Moving that TXT record to include the www prefix in the hostname will unblock it. The CNAME target changing is expected when a domain is deleted and re-added, as each addition generates a new target, and the current value in your DNS needs to be updated to the latest one shown in your dashboard settings.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago