Can you share the domain you’re trying to add?

This looks like a DNS authority and record-shape problem, not an app deployment problem.

The first thing I would check is which DNS provider is actually authoritative for the domain. If the nameservers point to Cloudflare, changes in MilesWeb's DNS panel will not be used. If the nameservers point to MilesWeb, Cloudflare proxy settings are not the active issue.

Run these for the real domain and subdomain:

dig NS yourdomain.com +short
dig CNAME your-subdomain.yourdomain.com +short
dig TXT _railway-verify.your-subdomain.yourdomain.com +short

Then make the records match what Railway shows in the custom domain screen:

1. Add the CNAME on the exact hostname you are connecting to Railway.

api.yourdomain.com -> xxxxx.up.railway.app

1. Add the TXT record on the exact verification name Railway gives you.

_railway-verify.api.yourdomain.com -> railway-verify=...

In many DNS panels, the host field should be only the left side, for example:

api
_railway-verify.api

not the full domain, because the panel appends the domain automatically.

1. Do not leave an A or AAAA record on the same hostname as the CNAME. A hostname cannot reliably have both an A record and a CNAME. Remove old A/AAAA records for that exact host.

2. If the domain really is using Cloudflare nameservers, set the Railway CNAME to DNS Only while verifying. A proxied orange-cloud CNAME can hide the real target from external verification. TXT records are not proxied, but the TXT name still has to be exact.

3. If you are trying to connect the root domain, such as yourdomain.com, check whether MilesWeb supports CNAME flattening, ALIAS, or ANAME. If it does not, use a subdomain like www.yourdomain.com or follow the exact apex-domain record Railway shows. Do not put a normal CNAME at the root unless your DNS provider supports flattening.

Once public DNS shows the expected values, Railway should verify it:

dig CNAME api.yourdomain.com @1.1.1.1 +short
dig TXT _railway-verify.api.yourdomain.com @1.1.1.1 +short

If those commands still show the old values, Railway is just reading stale or wrong authoritative DNS. Fix the record at the authoritative nameserver first, then retry verification.

my domain meeracreations.com

You need to add a TXT record to _railway-verify.meeracreations.com. Your CNAME record is also malformed.

I have added txt record but not working

In dnschecker.org dns record for cname shows as 6nasr4wr.up.railway.app for meeracreations.com

I checked the public DNS for meeracreations.com. The records are currently malformed.

The root domain is resolving as:

meeracreations.com -> 6nasr4wr.up.railway.app.meeracreations.com

and www is resolving as:

www.meeracreations.com -> meeracreations.com.meeracreations.com

That usually means the DNS panel is appending meeracreations.com to values that were entered as relative names.

Fix it like this:

1. For www.meeracreations.com, set the CNAME host to:

www

and set the value/target to the exact Railway target, for example:

6nasr4wr.up.railway.app

Do not enter it in a way that becomes 6nasr4wr.up.railway.app.meeracreations.com.

1. The TXT record for www verification is already visible publicly:

_railway-verify.www.meeracreations.com

so if Railway is verifying www.meeracreations.com, the main broken part is the CNAME target.

1. If you are trying to connect the root domain meeracreations.com, do not use a normal CNAME unless MilesWeb supports CNAME flattening, ALIAS, or ANAME at the root. Otherwise use www.meeracreations.com for Railway, or follow Railway's exact apex-domain record instructions.

After changing the record, check again with:

dig CNAME www.meeracreations.com +short

It should return the Railway target only, not a value ending in .meeracreations.com.

I got correctly as for cname 6nasr4wr.up.railway.app.meeracreations.com in checking www.meeracreations.com

in txt it is showing meeracreations.com.meeracreations.com.

Your CNAME should be the value provided by Railway. You should not modify the value. (It’s currently malformed)

The problem is that your DNS panel is appending meeracreations.com automatically.

For the CNAME, do not enter:

6nasr4wr.up.railway.app.meeracreations.com

Enter only this as the value:

6nasr4wr.up.railway.app

For the host/name field, use only the part Railway asks for. For example:

www

not:

www.meeracreations.com

For the TXT record, the same thing is happening. If it shows:

meeracreations.com.meeracreations.com

then you entered the full domain in a field where the DNS panel only wanted the short host.

Use the short host/name that Railway shows, without adding .meeracreations.com again. For example, if Railway asks for:

_railway-verify.meeracreations.com

then in MilesWeb the host/name field is probably only:

_railway-verify

If Railway asks for:

_railway-verify.www.meeracreations.com

then the host/name field is probably only:

_railway-verify.www

After saving, wait a few minutes and check again. The final records should not end with .meeracreations.com.meeracreations.com.

I have given this only host www and target 6nasr4wr.up.railway.app

Your current CNAME record ends with your domain, when it shouldn’t.

railway given me host name for txt: _railway-verify.www & a value

Again, your CNAME record is malformed. Check what you entered in your DNS provider.

TXT

Host/Name: _railway-verify.www

Value: paste the Railway TXT value exactly

For the CNAME, your host is correct:

CNAME

Host/Name: www

Target/Value: 6nasr4wr.up.railway.app.

The important part is the dot at the end of the CNAME target. Without that final dot, some DNS panels treat the target as a relative name and append your domain, which is why it becomes:

6nasr4wr.up.railway.app.meeracreations.com

After saving, delete any older wrong records for www or _railway-verify.www, then check these exact names:

www.meeracreations.com should return 6nasr4wr.up.railway.app.

_railway-verify.www.meeracreations.com should return the Railway TXT value

Do not put meeracreations.com in the host/name field. Use the short names: www for CNAME and _railway-verify.www for TXT.

I have given TXT

_railway-verify.www

railway-verify=bf8c8bed13daf31ab....

Your TXT is fine. Your CNAME isn’t. I’d just recommend migrating to Cloudflare’s DNS to avoid this headache.

I used cname

CNAME

Host/Name: www

Target/Value: 6nasr4wr.up.railway.app.