Custom domain www.caprockog.com on service caprock-site (project caprock-operating)

has been stuck in CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP for 7+ hours.

Your own API reports the DNS as correct and settled:

requiredValue = gkjtmp5t.up.railway.app

currentValue = gkjtmp5t.up.railway.app

status = DNS_RECORD_STATUS_PROPAGATED

The service has a successful deployment and serves fine on

caprock-site-production.up.railway.app. The custom domain serves your

CN=*.up.railway.app wildcard instead of a cert for the hostname, so browsers

fail with ERR_CERT_COMMON_NAME_INVALID.

Another custom domain on this same account works normally

(www.pluggingservices.com has a valid Let's Encrypt cert), so this is not an

account-level configuration problem.

Already tried: waited well past the 3600s TTL; called

customDomainUpdate(id, environmentId) to force revalidation (returned true, no

change); confirmed the domain is attached to the right service and environment.

Please manually trigger issuance, or tell me what is blocking validation.