Hi team,

A custom domain on my service has been stuck on "Waiting for DNS update" for over 24 hours and never provisions an SSL certificate, even though DNS is fully correct and propagated.

Project: CLR Builds and Automations (team workspace, Pro plan)

Service: CS Dashboard (the public web service, port 8080)

Domain: cs.cryptolabsresearch.com

Railway's expected CNAME target (as shown in the domain settings): 9g5wmtf3.up.railway.app

What I've verified independently:

• The CNAME for cs.cryptolabsresearch.com resolves to exactly 9g5wmtf3.up.railway.app, matching the target Railway displays.
• It resolves cleanly from the domain's authoritative HostGator nameservers (ns8521/ns8522.hostgator.com) at a 900s TTL, fully propagated (confirmed via Google DoH).
• That target resolves to your edge (69.46.46.121), and requests to https://cs.cryptolabsresearch.com reach Railway but are served the default *.up.railway.app wildcard certificate, so no per-domain cert has been issued.
• There are NO CAA records on cs.cryptolabsresearch.com or on the apex cryptolabsresearch.com, so Let's Encrypt issuance is permitted.
• status.railway.com shows everything operational.

I have removed and re-added the domain about 5 times (each re-add mints a new target, which I've re-pointed in DNS each time); the state never clears. This looks like a stuck certificate/ACME order on Railway's side for this specific domain. Could you force a fresh cert issuance for cs.cryptolabsresearch.com on the CS Dashboard service?

Thanks!