Hi everyone,

I have a custom domain stuck on "Waiting for DNS update" for several hours, even though both required DNS records are correctly configured and fully propagated.

The Railway dashboard requested:

- CNAME record pointing to the *.up.railway.app target

- TXT record at _railway-verify. with the railway-verify= value

I verified both records using dig against multiple public resolvers (Google 8.8.8.8, Cloudflare 1.1.1.1, Quad9 9.9.9.9, OpenDNS 208.67.222.222) and all of them return the expected values. The CNAME resolves correctly down to the Railway/Fastly IP, and the TXT value is byte-for-byte identical to what the "Configure DNS Records" modal shows in the dashboard.

Note: this is a simple subdomain on a registered root domain (not a www + root setup), so the advice from previous similar threads about adding TXT/CNAME on the root does not apply here.

What I have already tried:

1. Compared the values shown in the dashboard modal vs. the actual DNS responses (exact match, byte for byte)

2. Restarted the deployment via the Railway dashboard (Restart successful, but the "Waiting for DNS update" warning persists)

3. Looked for a manual "Verify" / "Recheck" button on the domain card, but there is not one (only Copy, Toggle CDN, Edit, Delete)

I also noticed the dashboard banner reporting an active incident about elevated numbers of queued deploys, which might be related to the domain validator being delayed.

Is there any way to manually trigger revalidation without removing and re-adding the domain (which would cause downtime on a production service)? Or does the team need to clear the validation cache on the backend?

I have seen at least 5 similar reports in the last 15 days that remain unresolved, so this might be a wider issue worth flagging.

Thanks in advance!