a month ago
been stuck at "Waiting for DNS update" for hours, across four add/remove cycles. No certificate issued; the domain returns empty. The Railway-provided domain works perfectly.
DNS matches Railway's own "Show DNS records" values exactly
Both confirmed via Google Public DNS, answered from the authoritative nameserver — not stale cache. GoDaddy registrar, GoDaddy nameservers, no proxy in front, port 3000 matches the working service domain.
can someone check server-side what's blocking verification, or force provisioning?
Pinned Solution
a month ago
If you’re using the API, make sure to add a TXT record at _railway-verify.<DOMAIN> where <DOMAIN> is the domain you’re trying to add. You can find the content for the record from the verificationToken property under status.
4 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
If you’re using the API, make sure to add a TXT record at _railway-verify.<DOMAIN> where <DOMAIN> is the domain you’re trying to add. You can find the content for the record from the verificationToken property under status.
0x5b62656e5d
What domain are you using?
a month ago
Financialvault.com
0x5b62656e5d
If you’re using the API, make sure to add a TXT record at `_railway-verify.<DOMAIN>` where `<DOMAIN>` is the domain you’re trying to add. You can find the content for the record from the `verificationToken` property under `status`.
a month ago
Bingo
Status changed to Solved 0x5b62656e5d • about 1 month ago