a month ago
My Custom domain is getting applied to frontend. Here is response from my domain provider.
I have measured this end to end. The DNS side is complete and correct — the remaining problem is inside your Railway project, and I can show you exactly where.
- Your DNS records are live and public
Confirmed just now from Cloudflare (1.1.1.1) and Google (8.8.8.8), not from our own server:
aangan.net.in A 69.46.46.97
www.aangan.net.in CNAME ojki7i9k.up.railway.app
_railway-verify.aangan.net.in TXT railway-verify=bee69fcf67effed4a71fbdbaffbc8bbac8273e3158bd89d2b52f9b1338c83737
69.46.46.97 is the same address ojki7i9k.up.railway.app resolves to, so your domain is pointing at Railway correctly. Nothing further is needed from us on DNS.
- Why you cannot reach the site — Railway is answering, and saying your domain is not linked to an app
Your traffic is arriving at Railway. When I request your domain, Railway itself replies:
{"status":"error","code":404,"message":"Application not found"}
That message comes from Railway's edge, not from us. It means the hostname aangan.net.in is not currently attached to any service inside your Railway project.
- Why the TXT is still yellow, and why HTTPS fails — both follow from the same thing
Railway is serving its own default certificate (*.up.railway.app) for your domain rather than one issued for aangan.net.in. Railway only issues a certificate after it has verified and attached the domain to a service. So the yellow marker, the missing certificate and the 404 are all one issue, not three.
The TXT record itself is definitely visible — I can read it from public resolvers, so nothing is missing on our end for Railway to find.
- What to do in Railway
Open your project → the service that should serve this site → Settings → Networking → Custom Domain.
Check aangan.net.in is listed under that service. If it is missing, or attached to a different service, add it there. This is the step that is most likely incomplete.
Press Railway's re-check / verify control next to the domain. Their check is on demand.
Note the root-domain point: Railway's instructions asked for a CNAME on @. A CNAME is not permitted at a domain's root — the DNS standard forbids it where the zone's own records live. The correct equivalent is an A record to Railway's address, which is what we have set. If Railway's screen insists on a CNAME at the root and will not accept the A record, the usual answer is to make www.aangan.net.in the primary custom domain, since that one is a true CNAME and already correct, and let the root redirect to it. Tell me if you would like that and I will set the redirect.
Thanks
Sudhir
1 Replies
Status changed to Awaiting Railway Response Railway • 28 days ago
a month ago
Both domains are attached to your "frontend" service, so the 404 is not caused by a missing link. For the root domain, your DNS and verification TXT are correct but the certificate workflow stalled, and we have started a certificate re-issuance that should complete within a few minutes. For the www subdomain, two DNS records at your registrar need fixing: the CNAME currently points to the wrong Railway target, and the TXT verification record at the host shown in your service's custom domain settings for that entry is missing entirely. You can find the correct CNAME target and the required TXT value on your service's Settings page under Networking, Custom Domains. Once those two records propagate, the www certificate will issue on its own.
Status changed to Awaiting User Response brody • 28 days ago
21 days 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 • 21 days ago