Custom domain SSL won't issue — stuck on CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP for hours across multiple attempts.

Project: 587111ae-e2b9-4d06-b3cf-43894cb798e5

Service (Web App): b833e505-8848-4334-a80e-ddfb499bc482

Environment (staging): 81feab2a-0c81-473e-8c86-63cbdb4fe1ba

Domain: www.dashduckies.dev → CNAME 0awd8b28.up.railway.app

Smoking gun: Polling the domain's status via the API, Railway's own dnsRecords[].currentValue flip-flops between the correct target and empty on consecutive polls:

railway-sees='0awd8b28.up.railway.app' status=DNS_RECORD_STATUS_PROPAGATED

railway-sees='' status=DNS_RECORD_STATUS_REQUIRES_UPDATE

railway-sees='0awd8b28.up.railway.app' status=DNS_RECORD_STATUS_PROPAGATED

railway-sees='' status=DNS_RECORD_STATUS_REQUIRES_UPDATE

This points to inconsistent internal DNS resolution / a stale edge cache on your side — external DNS is 100% consistent.

Already verified:

Public DNS correct + propagated on Google (8.8.8.8) and Cloudflare (1.1.1.1) → 0awd8b28.up.railway.app, and at GoDaddy's authoritative NS.

ACME challenge path reaches the Railway edge (x-railway-* headers present).

No CAA records on the domain.

certificateStatusDetailed, certificateErrorType, certificateErrorMessage are all null — no error surfaced.

Performed a full clean cycle (removed domain from Railway → removed CNAME from GoDaddy → waited 15 min → re-added domain → re-added CNAME → confirmed propagation). Still stuck.

Not rate-limited: 4 create attempts on this hostname, zero certs ever issued.

This is a .dev domain (HTTPS-only/HSTS) if relevant. Could you manually clear the stale edge/ingress DNS cache for this service + domain so the cert can validate? Thanks!