Custom domain stuck at VALIDATING_OWNERSHIP / REQUIRES_UPDATE despite clean DNS
pctech777
FREEOP
a month ago
Custom domain `app.shardapi.dev` (ID 17a8a220-ce06-40f5-a0a0-ed0a5eb94f9e)
on service pacific-hope/shard/production has been stuck for ~24h at:
certificateStatus: CERTIFICATE_STATUS_TYPE_VALIDATING_OWNERSHIP
dnsRecordStatus: DNS_RECORD_STATUS_REQUIRES_UPDATE
DNS is clean from the public internet:
$ dig +short CNAME app.shardapi.dev @1.1.1.1
1dheau6u.up.railway.app.
$ dig +short CNAME app.shardapi.dev @8.8.8.8
1dheau6u.up.railway.app.
$ dig +short CNAME app.shardapi.dev @9.9.9.9
1dheau6u.up.railway.app.
DNS provider: Cloudflare, proxy disabled (gray cloud), TTL 1m.
No conflicting A/AAAA records. Target matches the value Railway gave me.
This looks like the same pattern reported here, which a Railway employee
resolved by pushing the validator manually:
https://station.railway.com/questions/unable-to-validate-custom-domain-api-d-71d8b9da
Could someone re-trigger validation on this domain? Happy to provide
anything else useful.
Pinned Solution
a month ago
You need to add the TXT record provided by Railway.
2 Replies
Status changed to Open Railway • 27 days ago
a month ago
The content of the TXT record can be obtained from the verificationToken object under the status property in your GraphQL query.
It should be added to _railway-verify.app in your DNS table.
Status changed to Solved 0x5b62656e5d • 27 days ago