8 hours ago
Custom domain TXT verification stuck despite correct public DNS
Custom domain: www.upgrio.com
The domain has been stuck on “Waiting for DNS update” for 14+ hours.
CNAME verification is green in Railway.
The required _railway-verif.www TXT record has been added exactly as supplied by Railway.
The TXT record is publicly resolving correctly via Google Public DNS with NOERROR and the exact verification value supplied by Railway.
Could you please re-trigger domain verification / certificate issuance for www.upgrio.com?
I have not deleted or re-added the custom domain.
1 Replies
8 hours ago
The verification TXT record isn't resolving at the host we check, so ownership verification can't pass and the certificate is held until it does. The host needs to be _railway-verify.www (with the trailing "y"), while the record you described was created at _railway-verif.www, which is a different name.
Create a TXT record with host _railway-verify.www and value railway-verify=fb255e046e6e37e6c413efe69eab1910b792560aa234ee064830d966e24fc529. Your CNAME is already correct, so there is no need to remove or re-add the domain. Verification and certificate issuance continue on their own once the corrected record propagates.
Status changed to Awaiting User Response Railway • about 8 hours ago
Status changed to Solved upgrio • about 5 hours ago