Service: automation-platform (production environment)

Domain: ppu.wideout.com

The domain has been stuck on "waiting for DNS update" for about 8 days. Both required DNS records are in place and resolving globally with values matching exactly what the dashboard shows, but verification has never completed and no certificate has been issued.

Current DNS state:

$ dig ppu.wideout.com +short

8k5gnkh4.up.railway.app.

69.46.46.22

$ dig _railway-verify.ppu.wideout.com TXT +short

"railway-verify=c8a8feb713cc955f2fc5b90694fb22f3a22c97728d35fcc98f7b82ab2c1e8ed1"

Both match the dashboard values exactly. No conflicting A or AAAA records, and no CAA records on wideout.com.

Certificate status:

$ curl -Iv https://ppu.wideout.com 2>&1 | grep -i subject

• subject: CN=*.up.railway.app
• subjectAltName does not match host name ppu.wideout.com

Still serving the shared wildcard, so no cert has been issued for the custom domain. Browser shows ERR_CERT_COMMON_NAME_INVALID.

What we've already tried:

Deleted and re-added the custom domain twice; each cycle issued a new CNAME target and DNS was updated to match each time, with no change in status

Confirmed the domain is on the correct service and the production environment

The TXT record was initially missing (only the CNAME had been added). It has now been in place and resolving globally for over 2 hours with no change in status

Ask: could you force re-verification server-side? Given the delete/re-add cycles haven't helped and DNS has been verifiably correct for hours, this looks like a stalled verification job rather than a configuration issue on our end.