Title: Custom domain stuck on TXT verification despite correct public DNS

Hi Railway team,

my custom domain api.officestack.ai is stuck on “Waiting for DNS update” / TXT verification in Railway for almost 72 hours.

Project: truthful-dream

Service: officestack-backend

Environment: production

Custom domain: api.officestack.ai

Railway target shown in dashboard: 7290m4xs.up.railway.app

Railway shows:

• CNAME api → 7290m4xs.up.railway.app as verified
• TXT _railway-verify.api → still not verified / warning

However, public DNS resolves correctly from Google DNS:

nslookup -type=CNAME api.officestack.ai 8.8.8.8

returns:

api.officestack.ai canonical name = 7290m4xs.up.railway.app

and:

nslookup -type=TXT _railway-verify.api.officestack.ai 8.8.8.8

returns:

"railway-verify=2a8ac1d3e3c81bcc36190f8af13b60141f43d82bd24a331e1a1ec574409491fa"

HTTPS is still not working:

curl.exe -i https://api.officestack.ai/health

returns:

curl: (60) schannel: SNI or certificate check failed: SEC_E_WRONG_PRINCIPAL

Could you please manually re-check or re-trigger the domain ownership verification / certificate provisioning for this custom domain? DNS appears to be correct publicly, but Railway still does not verify the TXT record.