I'm trying to attach a custom domain (a www subdomain) to my service, and the dashboard has shown "Waiting for DNS update" for over 24 hours. I've independently verified the DNS is correct and has been the whole time.

Target Railway shows: a generated *.up.railway.app hostname, port 8080.

What I've verified independently:

Querying the domain's own authoritative nameserver directly returns the correct CNAME pointing at the exact target Railway gave me.

Querying Google's public DNS (8.8.8.8) returns the same, consistently, for over 24 hours.

No CAA record exists on the root domain that could be blocking Let's Encrypt from issuing a certificate.

No conflicting A/CNAME records on the subdomain — it's a single, clean CNAME.

Connecting directly to the subdomain on port 443 and inspecting the certificate shows Railway is still presenting its generic *.up.railway.app wildcard certificate, not one issued for my domain — so certificate issuance for this custom domain doesn't appear to have started, or is stuck.

Relevant history: the domain was originally added and assigned one target hostname. I later removed and re-added the domain, which generated a different new target hostname — I updated my DNS to match the new target immediately, and it's been correctly pointing at it ever since, per the checks above. Despite that, the dashboard still shows "Waiting for DNS update."

Has anyone else hit this? Is there a known fix, or does this need a Railway team member to manually re-trigger the cert/verification check on their end?