Skip to content
Custom domain stuck on waiting for DNS UPDATE
udcoinfs
OP

a month ago

Hi Railway team,

I need help with a custom domain that is stuck on "Waiting for DNS update".

Domain:

udcoineñafs.es

Railway custom domain:

xn--udcoineafs-z9a.es

Project:

humble-balance

Environment:

production

Service:

Udcoinena-fs

Railway-provided CNAME:

egz1wqdj.up.railway.app

Required TXT record:

Name: _railway-verify

Value: railway-verify=[REDACTED]

The domain is already active on Cloudflare and the CNAME and TXT records have been added exactly as shown by Railway.

I have also waited for propagation, but Railway still shows both DNS records with a warning and the custom domain remains "Waiting for DNS update".

When visiting https://udcoineñafs.es, Railway returns a "404 Not Found" page saying that the domain has not been provisioned.

Could you please check the DNS verification status for this custom domain and tell me why Railway is not validating the CNAME/TXT records?

Thank you.

Solved

1 Reply

Railway
BOT

a month ago

The custom domain saved on your service is not the same hostname as the domain you own on Cloudflare. In encoded form it has one extra letter, so it is a different name. The CNAME and TXT records you created belong to your real domain's zone, so our check for the saved hostname finds no records, and verification cannot complete.

To fix it, remove the custom domain from the service's Settings and add it again, typing the domain exactly as registered. The new entry gets a new CNAME target and a new _railway-verify TXT value. Update both records in Cloudflare to the values the dashboard shows for the new entry.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway
BOT

a month ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...