Hi Railway team,

I'm experiencing an issue with custom domain validation that's been stuck for over 40 minutes.

Domain: www.blockstories.io

Project: landing-page

Current Status: "Validating domain ownership"

DNS Configuration:

- Type: CNAME

- Name: www

- Value: nksm8ayh.up.railway.app

- Verified via dig from multiple locations (8.8.8.8, 1.1.1.1)

- TTL: 600 seconds

- DNS propagated: Confirmed working globally

SSL Certificate Issue:

When accessing www.blockstories.io, the browser shows a certificate error (NET::ERR_CERT_COMMON_NAME_INVALID) because it's serving the *.up.railway.app wildcard certificate instead of one for www.blockstories.io. I can access the site by clicking "Advanced → proceed to unsafe website" in the browser, which confirms the DNS is routing correctly to Railway, but the SSL certificate hasn't been provisioned due to the validation being stuck.

What I've tried:

1. Waited 40+ minutes for validation

2. Deleted and re-added the domain (received new CNAME value)

3. Verified DNS propagation with dig commands

4. Checked no conflicting DNS records

App Status:

- Working correctly at: landing-page-production-b455.up.railway.app

- Health endpoint responding: /api/health

Issue:

The custom domain validation appears stuck at "Validating domain ownership" stage, preventing SSL certificate provisioning. The DNS is correctly configured and routing traffic to Railway (confirmed by bypassing the certificate warning), but validation hasn't completed.

Could you please check if there's an issue with the validation process for this domain? The DNS routing is working, but the ownership validation seems stuck.

Thanks!