Custom domain stuck at “Waiting for DNS update” despite DNS resolving correctly

Question

My custom domain greenmeansusa.com remains stuck at “Waiting for DNS update.”

The Railway service itself is healthy and the Railway-generated domain works correctly. The custom domain is attached to the service on port 8080.

I have independently checked the required DNS records using both Google Public DNS (8.8.8.8) and Cloudflare DNS (1.1.1.1).

Both resolvers return the expected CNAME pointing to the Railway-provided target, and both return the expected _railway-verify TXT record.

I have also checked for an apparent CAA or DNSSEC problem and did not find one.

Since the required records are publicly resolving but Railway continues to show “Waiting for DNS update,” is there something else that can cause Railway's domain verification to remain stuck?

Is there a way to force Railway to re-check the existing domain attachment, or should the custom domain be removed and re-added?

I have already gone through the DNS configuration multiple times, so I would prefer not to change working DNS records unless there is a specific reason.