a month ago
Title: Custom domain TXT stuck on warning despite verified DNS records - ibawritten.com
CNAME shows verified (green) but TXT verification stays on warning (yellow) and never completes, despite the DNS records being correctly published and confirmed via public resolvers. The CNAME status also intermittently flaps between green and warning on its own.
Domain: ibawritten.com
Project: ab1febd1-2cf4-42a8-a5de-a234530e3243
Service: 403fa149-0a3f-4813-9a2b-18caa5e209df/
What I've verified:
- TXT record resolves correctly from a public resolver (Google DoH / 1.1.1.1):
_railway-verify.ibawritten.com TXT → railway-verify=e7ad5bc5bac081ed52847282e15f0badd43232615994e56a7a770e5664e05562
(single record, full 64-character token, matches what's shown in the Railway dashboard)
-
No CAA restrictions on the domain — CAA lookup returns no Answer records at all, so no authority is blocking issuance.
-
Tested with Cloudflare proxy both ON (orange cloud) and OFF (DNS only) — same result either way, TXT stays yellow.
Since DNS is provably correct on my end and this has persisted across multiple checks and both proxy modes, could a moderator manually re-trigger the domain verification workflow for this domain?
Happy to provide anything else needed.
screenshots of the Railway domain settings page, timestamps, etc.
Attachments
2 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Your DNS records are correct - both the CNAME and the TXT verification record at _railway-verify.ibawritten.com are propagated and match what we expect. The verification workflow stalled before it could pick up your DNS changes, so it never re-ran. We've started a certificate re-issuance for this domain, which should complete verification and issue the TLS certificate within a few minutes.
Status changed to Awaiting User Response sam-a • about 1 month ago
a month ago
Thanks!
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Solved Railway • about 1 month ago