Please click "see instructions" and try following those instructions to setup the DNS. Let us know if that does not resolve the issue.

I did, it was working before just fine, but randomly stopped working and don't find the CNAME record

Are you able to follow the instructions that show up? If not, what error are you getting?

I'm not getting any error it's basically not working anymore like the DNS record doesn't exists anymore in cloudflare, but the record it's still present, nothing changed

Looks like the domain points to an AWS IP -

https://www.nslookup.io/domains/mysticgold.app/dns-records/#google

I would also like to note, if you have SSL / TLS set to Full (Strict) in Cloudflare -- we don't support that.

Railway is not working on AWS, that's why it's showing aws ip?

We do not use AWS or any other Cloud provider.

Your domain is pointed to the wrong value.

And i use Full, not Full (Strict)?

Unfortunately, we will not be able to assist further here as the issue is outside of Railway's control.

I will step away from this thread to let the community help you.

No, sorry was not a question, I confirmed that i am using Full not Full(Strict)

Hi, I’ve run into the same situation before. If your Railway custom domain suddenly shows "Waiting for DNS updates" and you haven't changed anything, but you're using Cloudflare, there are a few likely reasons.

1. Cloudflare proxy (orange cloud) is enabled

Railway needs to verify your domain by resolving the actual target (your-app.up.railway.app). If the Cloudflare proxy is enabled, Cloudflare returns its own IPs, and Railway can't confirm the record.

What to check:
Go to your Cloudflare DNS settings and make sure the CNAME record for your domain is set to “DNS only” (grey cloud), not proxied.

2. CNAME or A record is missing or incorrect

Sometimes DNS records can be accidentally removed, expire, or get modified by other services or automation (e.g., SSL apps, email services).

What to do:
Double-check that the record still exists and is pointing exactly to the value Railway gave you (usually something.up.railway.app).

You can verify using:

dig yourdomain.com @8.8.8.8

Or use dnschecker.org to check globally.

3. Railway got stuck

Occasionally, even with correct DNS, Railway's status might not update.

Try:

• Clicking “Refresh DNS” in the Railway domain settings

• Removing the domain and adding it again (brief downtime)

• Contacting Railway support if it persists

Hey! A few quick things to check:

1. In Cloudflare, make sure your CNAME is set to DNS only (gray cloud), not proxied.

2. Double-check that the CNAME is pointing to the correct target Railway gave you.

3. In Railway, try removing the domain and re-adding it—it usually forces a fresh DNS check.

4. You can also use dnschecker.org to see if your records are actually propagating.

Let me know what you find and I can help further if needed.

Are you able to follow the instructions that show up? If not, what error are you getting?