a month ago
Project: blog-nodejs (service: blog-nodejs)
Custom domain: blogdealffa.com
Status: "Waiting for DNS update" for more than 24 hours
Confirmed on my end:
-
ALIAS record pointing to xjegp397.up.railway.app (updated ~1 hour ago)
-
TXT record railway-verify=5875a76f93a796526e95e87f6dfeca03092cddade1ef1eaa0563feb9af4a419b (present)
-
dig confirms DNS has already propagated correctly (IP 69.46.46.82)
-
The original domain got stuck during the "Deployments slow to start" incident
(Degraded Performance, resolved August 29 03:38 UTC)
-
I already tried removing and re-adding the domain, with no change in result
Could you please manually review the verification for this domain?
1 Replies
a month ago
The verification TXT record is currently placed on the root domain, but it needs to be on the _railway-verify subdomain instead. At Porkbun, create a TXT record with the host/name set to _railway-verify and the value shown in your Railway dashboard under the domain's DNS settings, then remove the TXT record from the root. Once the new record propagates, verification and certificate issuance should proceed automatically.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago