a month ago
I have two projects with two domains www.premiermotorsve.com and www.hondamaracaibo.com where the DNS records are set up well but the verification hasnt happened.
I reviewed the DNS and they are up but railway doesnt recognize them
Attachments
8 Replies
a month ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 28 days ago
a month ago
1. The www CNAME to Railway's target is missing or wrong - The image only proves the _railway-verify TXT is propagated. It says nothing about the actual routing record. Railway's verification typically checks both the TXT token and that www.<domain> resolves to its assigned target (<something>.up.railway.app). A propagated TXT alone will not flip the status - if the www CNAME isn't there, or still points to the old host (parked page, GoDaddy forwarding, Cloudflare proxy, previous provider), Railway stays stuck on "verifying".
2. The two projects verification tokens got swapped
rotemw1991
1\. The `www` CNAME to Railway's target is missing or wrong - The image only proves the `_railway-verify` TXT is propagated. It says nothing about the actual routing record. Railway's verification typically checks both the TXT token and that `www.<domain>` resolves to its assigned target (`<something>.up.railway.app`). A propagated TXT alone will not flip the status - if the `www` CNAME isn't there, or still points to the old host (parked page, GoDaddy forwarding, Cloudflare proxy, previous provider), Railway stays stuck on "verifying". 2\. The two projects verification tokens got swapped
a month ago
I have the CNAME of the subdomain www on green check by railway but the TXT isnt on a green check, that is the issue, I simply added the domain also to the DNS because of railway advice but it still doesnt recognize the TXT of the subdomain
25 days ago
I did the NS lookup and the record is there, but Railway wont pick it up, the record is correctly setted with _railway-verify.www , so I dont understand why the error.
Attachments
rotemw1991
1\. The `www` CNAME to Railway's target is missing or wrong - The image only proves the `_railway-verify` TXT is propagated. It says nothing about the actual routing record. Railway's verification typically checks both the TXT token and that `www.<domain>` resolves to its assigned target (`<something>.up.railway.app`). A propagated TXT alone will not flip the status - if the `www` CNAME isn't there, or still points to the old host (parked page, GoDaddy forwarding, Cloudflare proxy, previous provider), Railway stays stuck on "verifying". 2\. The two projects verification tokens got swapped
24 days ago
I did the NS lookup and the record is there, but Railway wont pick it up, the record is correctly setted with _railway-verify.www , so I dont understand why the error.
guidation
I did the NS lookup and the record is there, but Railway wont pick it up, the record is correctly setted with \_railway-verify.www , so I dont understand why the error. 
23 days ago
Try removing and readding the records.
medim
Try removing and readding the records.
21 days ago
I tried but nothing, the records do not seem to update in Railway as the check is still there for records that are no longer up, is there a way to manually update the Railway lookup?
medim
Try removing and readding the records.
18 days ago
It seams Railway doesnt update this DNS reocrds, and the same error persists, dont know what to do anymore, my project is stucked because of this error.