Quick update on my previous issue:

Since there’s no refresh/recheck option in Railway, I removed the domain and added it again. This time, the domain got approved successfully.

However, I noticed something confusing:

• The TXT record remained exactly the same
• The CNAME record value changed
• My DNS manager is still using the old CNAME
• Despite that, the website is working correctly

My questions:

1. Should I update my DNS to use the new CNAME provided by Railway, or is it safe to keep the old one since everything is currently working?
2. Is there any recommended way to avoid this kind of issue in the future, given that there’s no manual refresh/recheck option for DNS verification?

Would appreciate clarification on how Railway handles CNAME changes internally.

I am having this problem now and it is causing me so much stress. I don't know what else to do I have added and readded the domain and udated the records and it still doesnt work

Any update from the team on this?

I’m seeing more users running into the same TXT verification issue, and the only workaround so far seems to be removing and re-adding the domain.

In my case, re-adding fixed it, but introduced another ambiguity:

• Railway generated a new CNAME
• The old CNAME is still in my DNS
• Everything still works, which suggests Railway may still accept the old target

This creates uncertainty about whether:

• The old CNAME is still officially valid, or
• It’s temporarily working and could break later

It would help to clarify:

1. Whether CNAME targets can change and require manual updates
2. If old CNAMEs remain valid indefinitely or are eventually deprecated
3. Whether a proper “recheck/refresh DNS” feature is planned to avoid needing domain re-creation

Right now, the lack of a refresh mechanism makes debugging DNS issues unnecessarily disruptive.

same problem here but mine doesnt work at all

Agh

I'm hoping they'll add a recheck/refresh feature, even after removing/readding my domain the CNAME won't verify 😢