2 months ago
My custom domain neverdue.ca has been stuck on "Validating domain ownership"
for several hours. All DNS records resolve correctly:
$ dig CNAME neverdue.ca +short
uiqhhh6q.up.railway.app.
$ dig TXT _railway-verify.neverdue.ca +short
"railway-verify=f1e165e88d7825c0d27d7ca91196e6a8c8784e6a16d03336186433d34f5d6109"
Both return the correct values Railway provided. I've successfully used
Railway with .me domains before with no issues. Seems specific to .ca TLD
or a bug on Railway's side. Anyone seen this?
4 Replies
2 months ago
Hey, I did a nslookup on neverdue.ca and I don't see the verification TXT record there, it seems you're incorrectly placing it on the _railway-verify.neverdue.ca subdomain instead.
Railway explicitly instructs adding the TXT record with host _railway-verify,
which creates _railway-verify.neverdue.ca. That record resolves correctly:
$ dig TXT _railway-verify.neverdue.ca +short
"railway-verify=f1e165e88d7825c0d27d7ca91196e6a8c8784e6a16d03336186433d34f5d6109"
The root CNAME on @ is causing TXT lookups on neverdue.ca to return the CNAME
instead. Is Railway's validator checking the root domain or the _railway-verify
subdomain specifically?
Attachments
2 months ago
I see that the domain is working (cool website design btw), I will mark this as solved
Status changed to Solved medim • about 2 months ago