Custom domain stuck on "Waiting for DNS update" despite confirmed propagation
tiagoarlindo
FREEOP

2 months ago

I have a custom domain, app.linkimobi.pt, attached to the service easygoing-endurance in the project exciting-beauty.

The CNAME record and the TXT verification record are both correctly configured and confirmed as fully propagated globally, checked via dnschecker.org, for both the CNAME and the TXT values.

Despite this, the domain remains stuck at "Waiting for DNS update" in the Railway dashboard.

I already removed and re-added the custom domain once, updating the DNS records to match the new CNAME value generated by Railway at that time, but the issue persists.

Could you check if there is a verification issue on Railway's side for this specific domain?

Domain: app.linkimobi.pt

Service: easygoing-endurance

Project: exciting-beauty

Captura de ecrã 2026-07-04 152035.png

Captura de ecrã 2026-07-04 152018.png

Solved$10 Bounty

Pinned Solution

You have an invalid TXT record. The value after "railway-verify=" must be exactly 64 characters, but yours contains 33.

2 Replies

Railway
BOT

2 months ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway about 2 months ago


You have an invalid TXT record. The value after "railway-verify=" must be exactly 64 characters, but yours contains 33.


I suggest you remove your custom domain, and all its related DNS records, and add it again with correct values. Make sure you copy the entire TXT value using the copy button.


Status changed to Solved tiagoarlindo about 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...