Hi — my custom domain fleet.mediccarellc.com (service web, project amused-peace, production environment) has been stuck on "Waiting for DNS update" for over 12 hours. The CNAME shows verified (green ✓); only the TXT verification record shows the warning.

The DNS is correct and fully propagated. dig returns the single expected value, byte-for-byte matching what the Configure DNS Records modal shows:

$ dig _railway-verify.fleet.mediccarellc.com TXT +short

"railway-verify=852bb542b82ceeb0b2a01c85199daee4d08afbf9fcdd04401d146d4f9b67a509"

The CNAME also resolves correctly:

$ dig fleet.mediccarellc.com CNAME +short

→ n3j1rpzm.up.railway.app

DNS is hosted directly on GoDaddy (no Cloudflare proxy). The service is deployed and online (the *.up.railway.app domain works fine). There was previously a duplicate/truncated TXT record, which I removed — dig now confirms only the single correct value is published.

This appears to be a verification-state issue on Railway's side rather than a DNS problem. Could you manually re-trigger verification / clear the validation cache for this domain? I'd prefer to avoid removing and re-adding the domain due to Let's Encrypt rate limits, given prior cert attempts on it.

Thanks!