a month ago
Custom domain www.channelbrief.net on service "tubedigest-landing" (project TUBEDIGEST LANDING) has been stuck on "Validating domain ownership" for over 2 hours.
DNS is confirmed correct via multiple independent resolvers (Google DNS 8.8.8.8, Cloudflare):
- CNAME www.channelbrief.net -> vb2olxxl.up.railway.app (resolves correctly)
- TXT _railway-verify.www.channelbrief.net -> correct verify token (matches what Railway provided)
- No CAA records blocking certificate issuance
- Domain's nameservers are Cloudflare (rob.ns.cloudflare.com, venus.ns.cloudflare.com), fully propagated
What makes this look like an isolated/stuck job rather than a DNS problem:
- app.channelbrief.net (same root domain, different service in the same project) verified almost instantly
- www.tubedigest.pl on this exact same service (tubedigest-landing) also works fine
- I originally added www.channelbrief.net, it got stuck, so I deleted the custom domain and re-added it (got a new CNAME target vb2olxxl.up.railway.app and it's still stuck the same way)
Could someone check the domain verification queue/job for this specific domain on your end? Happy to provide any additional info (service ID, project ID, screenshots).
1 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
It may take up to a few hours (maybe even a day) for Railway to validate the DNS and issue certificates. If one isn't issued by then, try removing the domain from Railway and add it back after ~10-15 mins. Update DNS records as necessary.