22 days ago
Same bug as my ticket from 6 days ago (marked Solved 5 days ago, resolved by staff member
0x5b62656e5d for portal.scionmediadigital.com). New custom domain added tonight has been stuck for 1+
hour now.
Details:
- Project: Scion Media Digital OS (828cdd94-c08f-420a-97ea-aa3435feee03)
- Service: solidgold-dashboard (6f996757-dabf-43b2-ba6a-ed6788a747ce)
- Environment: production (16b93733-9d32-4c5d-996e-8a8bb5ac22dd)
- Custom domain: sightline.scionmediadigital.com
- Domain ID: e95c13da-d172-452f-ad24-88fbe5ba30b0
- Created: 2026-04-23T02:30:25 UTC
What I've verified on my end:
- DNS propagated: CNAME → n94siv02.up.railway.app (confirmed via dig @1.1.1.1; your status endpoint
shows DNS_RECORD_STATUS_PROPAGATED)
- No CAA records blocking Let's Encrypt on scionmediadigital.com
- Cloudflare proxy is OFF
- ACME challenge path /.well-known/acme-challenge/ reachable on port 80 (Railway edge returns
expected 404 when no active challenge)
- Already tried delete + recreate once
Can you manually retrigger ownership validation like you did for the portal. domain 5 days ago? Happy
to add another bounty.
Pinned Solution
22 days ago
You need to add a TXT record. I ran nslookup on sightline.scionmediadigital.com and I got NXDOMAIN.
6 Replies
22 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • 22 days ago
22 days ago
Ok awesome. is this a good thing? new here
22 days ago
You need to add a TXT record. I ran nslookup on sightline.scionmediadigital.com and I got NXDOMAIN.
22 days ago
Thanks for the quick look! I can't reproduce the NXDOMAIN — DNS is propagated on all major resolvers
and your own API confirms it:
$ dig @1.1.1.1 sightline.scionmediadigital.com +short
151.101.2.15
$ dig @8.8.8.8 sightline.scionmediadigital.com +short
151.101.2.15
$ nslookup sightline.scionmediadigital.com
Non-authoritative answer:
sightline.scionmediadigital.com canonical name = n94siv02.up.railway.app.
And your own status endpoint for domain e95c13da-d172-452f-ad24-88fbe5ba30b0 returns:
status: DNS_RECORD_STATUS_PROPAGATED
currentValue: n94siv02.up.railway.app (matches requiredValue)
certificateStatus: CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP
The dnsRecords field in your API only lists the CNAME requirement — no TXT record appears in the
requirements. Could you tell me exactly what TXT record name + value you need? (e.g.,
railway-verify.sightline... → <value>, or acme-challenge.sightline... → <value>?) — I'll add it
immediately once I have the specifics.
Also happy to try once more from your end — this is the same symptom as the ticket you solved 5 days
ago for portal.scionmediadigital.com, and no TXT record was needed then.
22 days ago
nslookup -type=TXT _railway-verify.sightline.scionmediadigital.com
Server: 100.100.100.100
Address: 100.100.100.100#53
** server can't find _railway-verify.sightline.scionmediadigital.com: NXDOMAINIn the API, the TXT value can be obtained from the verificationToken field.
Assuming you're calling the domains query, the token is under customDomain > status.
22 days ago
---
TXT record added. Verified propagating on 1.1.1.1 within seconds:
$ dig @1.1.1.1 TXT _railway-verify.sightline.scionmediadigital.com +short
"railway-verify=2aed7b96abbd08f60c0fa6f36f4e946abc1f8139c9ca962016e1d59f5f0dd0c1"
Please re-trigger validation whenever you're able. Thanks!
22 days ago
Is the domain validated in your dashboard?
Railway should have automatically detected the DNS change within the hour.
Status changed to Solved 0x5b62656e5d • 18 days ago