7 days ago
I've got ANAME set in Dynadot, but Railway just refuses to confirm it. I've deleted, waited, re-added etc. - www confirming fine of course.
It's like ANAME won't suffice for the CNAME requirement, which I thought was the whole point of an ANAME. Help?
2 Replies
7 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 7 days ago
7 days ago
Railway requires both a CNAME and a TXT record for ownership verification — when you add a custom domain, Railway gives you a CNAME value and a TXT record, and both are required; the domain won't verify with only the CNAME in place. If you've only set up the ANAME and skipped the TXT record, that alone would block verification
Confirm the TXT record is also present and exact. Easy to miss — go re-check the Railway dashboard's exact TXT name/value pair.
Run dig yourdomain.com TXT and dig yourdomain.com CNAME (or ANAME) externally — confirm what's actually being served, not just what Dynadot's UI shows. ANAME records get "flattened" into A records by the registrar, so a CNAME-type DNS query may legitimately return nothing, which could be exactly what's tripping up Railway's verifier if it's checking the wrong record type
7 days ago
Unfortunately, ANAME didn't work from Dynadot and had to go Cloudflare route. Quite irritating. Railway should fix this IMO.