15 days ago
Custom domain command.spartisbiologics.com remains stuck on “Validating domain ownership” and serves the default *.up.railway.app certificate.
Affected service: exciting-radiance / production.
Verified:
- The required CNAME points to the exact Railway target shown in the dashboard.
- The required _railway-verify.command TXT value exactly matches the Railway dashboard.
- Both records resolve from GoDaddy authoritative DNS and public resolvers including 1.1.1.1, 8.8.8.8, and 9.9.9.9.
- There are no conflicting A or AAAA records.
- There is no restrictive CAA record.
- DNSSEC is not enabled.
- The application is healthy on its Railway-generated URL and the custom hostname routes to the correct Railway application when certificate verification is bypassed.
The domain has been removed and re-added once after DNS propagation, but validation remains pending. Is there a backend ownership-validation state that Railway support must refresh, or another diagnostic available for this condition? No application, database, or DNS changes are requested.
1 Replies
15 days ago
Your domain is actually verified and the certificate is valid on our side, so the "validating" state you see may be a stale dashboard view. The one issue is that your CNAME record currently points to oezbxzvz.up.railway.app, but the required target shown in the dashboard is 46htbjoc.up.railway.app. Update the CNAME at GoDaddy to point to 46htbjoc.up.railway.app and the domain should serve correctly with its own certificate once the DNS change propagates. Reply here once you have updated it and we can verify the change took effect.
Status changed to Awaiting User Response Railway • 15 days ago
8 days 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 • 8 days ago