Sometimes it might take 24 hours for domain ownership validation. Wait a few more hours

If a certificate isn't issued by Railway within a day, try to remove your custom domain and all its related DNS records, wait for 10 - 15 minutes, and add it again.

This looks like it's stuck on Railway's own validation side, not yours. I hit a very similar pattern today on a different domain: Railway's own customDomain status check reported a stale DNS value for over an hour after the actual DNS had already updated correctly (independently confirmed via dig against the authoritative server) — the discrepancy was entirely on Railway's internal checker lagging behind real DNS state, not anything wrong with the domain config.

Two things worth trying while waiting on staff:

1. Remove and re-add the custom domain in Networking to force a fresh validation attempt (this reset Railway's internal state for me, even if it didn't fully resolve the issue on its own).
2. Check status.railway.com for any ongoing incidents around domain validation — if there's a known backend issue right now, that'd explain both cases at once.

Given DNS is this cleanly verified across multiple independent sources including the authoritative server, this looks like something that needs a Railway staff member to manually check/kick the validation on their end — not a config problem on your side.