Custom domain TXT is public but Railway still says missing

Question

Hi Railway team,

We’re trying to verify the custom domain `ads.prequel.co`.

Railway is asking us to add:

Type: TXT

Name: \_[railway-verify.ads](http://railway-verify.ads)

Value: railway-verify=a48de91b223c85b99b4d5a2eaf8eaa556bdc3b43c20e9062405762a180562bb8

The record appears to be live publicly, including from Cloudflare authoritative DNS and public resolvers.

Current checks:

TXT:

\_[railway-verify.ads.prequel.co](http://railway-verify.ads.prequel.co) \= railway-verify=a48de91b223c85b99b4d5a2eaf8eaa556bdc3b43c20e9062405762a180562bb8

CNAME:

[ads.prequel.co](http://ads.prequel.co) \= [a1smp4o9.up.railway.app](http://a1smp4o9.up.railway.app)

HTTP reaches Railway edge:

<http://ads.prequel.co/%5F%5Ftempa-domain-check%5F%5F> returns 301 to HTTPS with `Server: railway-edge`.

HTTPS still serves the Railway wildcard certificate:

CN=\*.[up.railway.app](http://up.railway.app)

SAN=DNS:\*.[up.railway.app](http://up.railway.app)

The custom domain is set to port 8080.

Could you please force a recheck / refresh the validation state for `ads.prequel.co`, or tell us what Railway is seeing that makes the TXT check fail?