Got it. DNS is correct at Hostinger. The problem is Railway still hasn't provisioned `srt1.io` on their end. This happens when: 1. Railway sees the DNS pointing to them 2. But they haven't validated and issued the SSL certificate yet 3. So the domain stays in "Not Found" state **What you need to do:** Contact Railway support directly. Tell them: * Domain: `srt1.io` * Service: web * Project: SRT1 * DNS is correctly pointing to `web-production-91b8f.up.railway.app` * Domain still shows "Not Found" error They can manually trigger the provisioning on their backend. This is a known issue when domains don't auto-provision despite correct DNS. You can reach them at: or through your Railway dashboard.

DNS is correct at Hostinger. The problem is Railway still hasn't provisioned srt1.io on their end.

seedclassintelligence

HOBBYOP

a month ago

Got it. DNS is correct at Hostinger. The problem is Railway still hasn't provisioned srt1.io on their end.

This happens when:

Railway sees the DNS pointing to them
But they haven't validated and issued the SSL certificate yet
So the domain stays in "Not Found" state

What you need to do:

Contact Railway support directly. Tell them:

Domain: srt1.io
Service: web
Project: SRT1
DNS is correctly pointing to web-production-91b8f.up.railway.app
Domain still shows "Not Found" error

They can manually trigger the provisioning on their backend. This is a known issue when domains don't auto-provision despite correct DNS.

You can reach them at: https://railway.com/support or through your Railway dashboard.

Solved

4 Replies

Railway

BOT

a month ago

Your domain srt1.io is a root/apex domain, and your DNS is currently using Hostinger's nameservers (ns1.dns-parking.com, ns2.dns-parking.com) which do not support CNAME flattening. The CNAME record we require for traffic routing is not resolving (public DNS shows an A record of 151.101.2.15 instead of pointing to your Railway CNAME target). Your TXT verification record is present and correct, but the SSL certificate cannot be issued until the CNAME is properly resolving. To fix this, you need to switch your domain's nameservers to a provider that supports CNAME flattening at the root, such as Cloudflare, as described in our docs.

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

Railway

Your domain `srt1.io` is a root/apex domain, and your DNS is currently using Hostinger's nameservers (`ns1.dns-parking.com`, `ns2.dns-parking.com`) which [do not support CNAME flattening](https://docs.railway.com/networking/domains/working-with-domains#adding-a-root-domain). The CNAME record we require for traffic routing is not resolving (public DNS shows an A record of `151.101.2.15` instead of pointing to your Railway CNAME target). Your TXT verification record is present and correct, but the SSL certificate cannot be issued until the CNAME is properly resolving. To fix this, you need to switch your domain's nameservers to a provider that supports CNAME flattening at the root, such as Cloudflare, as described in our [docs](https://docs.railway.com/networking/domains/working-with-domains#adding-a-root-domain).

seedclassintelligence

HOBBYOP

a month ago

Hostinger currently shows the root @ record as an ALIAS to web-production-91b8f.up.railway.app (TTL 300).

Your www record also points to the same Railway target, and the domain is using Hostinger nameservers (ns1.dns-parking.com / ns2.dns-parking.com).

So the DNS zone at Hostinger is already set correctly; Railway’s note appears to be based on a stale or different public DNS check.

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

seedclassintelligence

HOBBYOP

a month ago

HELLO CAN I LIVE ASSISTANCE

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

chandrika

EMPLOYEE

a month ago

Hey — I just ran a fresh DNS check against public resolvers, and the records aren't resolving to Railway yet:

srt1.io returns an A record of 151.101.2.15 (a parking/default IP, not Railway)
No CNAME record is resolving for srt1.io
No _railway.srt1.io TXT verification record found
Nameservers are ns1.dns-parking.com / ns2.dns-parking.com

The core issue is that Hostinger's dns-parking.com nameservers do not support CNAME flattening for root/apex domains. Even if you've added an ALIAS record in Hostinger's UI, these nameservers can't resolve it — so public DNS still returns the old parking IP instead of routing to Railway.

To fix this, you have two options:

Switch your nameservers to Cloudflare (free plan works). Cloudflare supports CNAME flattening at the root. Once you switch, add:
- A CNAME record for @ (root) pointing to web-production-91b8f.up.railway.app
- A TXT record for _railway with the verification value from your Railway dashboard
Use www.srt1.io instead — add a CNAME for www pointing to your Railway target (CNAMEs on subdomains work with any DNS provider), and set up a redirect from the root domain to www.

Our docs on adding a root domain cover this in more detail. Once the CNAME resolves correctly from public DNS, Railway will automatically provision the SSL certificate.

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!