Unable to verify institutional domain on Railway — DNS records already propagated
ryanolivrdev
PROOP

10 days ago

Hello,

I’m trying to verify the institutional domain cria.cesupa.br, but I’m stuck on the domain verification step.

The requested DNS records are already configured and publicly propagated.

For cria.cesupa.br

CNAME:

cria.cesupa.brntrx5651.up.railway.app

TXT verification record:

_railway-verify.cria.cesupa.br

Returned value:

railway-verify=e9de993248e73ebdec84e21270481ec98ea71d0d6accda839f1ddfa7699777ac

The DNS query returns NOERROR, and the TXT record is showing correctly.

For www.cria.cesupa.br

CNAME:

www.cria.cesupa.brzkr07lxt.up.railway.app

TXT verification record:

_railway-verify.www.cria.cesupa.br

Returned value:

railway-verify=5f9c04cbdd829398fb80798d99caa4eed8b4033390528152f8e463327f614c38

The DNS query also returns NOERROR, with the TXT record showing correctly.

However, Railway still does not recognize the domain verification. Also, the retry/re-verify option is not working or is not available for me.

Since this is an institutional domain, I don’t have full control over the DNS provider, but the requested records have already been added by the responsible team and are publicly resolvable.

Could you please force a manual re-check or unlock the domain verification process for these domains?

Domains/projects:

cria.cesupa.br

www.cria.cesupa.br

Thank you.

Solved$20 Bounty

1 Replies

Railway
BOT

10 days ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open Railway 10 days ago


Railway usually validates the DNS and issues the certificates within the hour, but although rare, it may take up to a day.

If Railway doesn't issue the certificates within a few hours, I'd try removing the domain from Railway and adding it back after ~10-15 mins and update DNS records if necessary.

Also, make sure to access the sites using an incognito window when checking, as your browser may be storing stale data (eg, invalid certificates).


Status changed to Awaiting User Response Railway 10 days ago


Status changed to Solved ryanolivrdev 10 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...