Custom domain stuck on "Waiting for DNS update" even though DNS is correctly configured
jaymarvaniya5591
FREEOP

3 months ago

Hi, I'm trying to connect my custom domain boldoai.in to my Railway service, but the domain has been stuck on "Waiting for DNS update" for quite a long time.

Here is what I have done so far:

  1. Railway provided these DNS instructions:
    • CNAME @ → y9qbkl7s.up.railway.app
    • TXT _railway-verify → railway-verify=...
  2. In my DNS provider (Hostinger) I added:
    • ALIAS @ → y9qbkl7s.up.railway.app
    • TXT _railway-verify → railway-verify=...
  3. DNS propagation appears to be complete. When I run:
nslookup boldoai.in 8.8.8.8

I get:

boldoai.in → 66.33.22.2

which I believe is Railway's edge/load balancer IP.

  1. DNS checker also shows the same IP globally.

However, inside Railway the domain status still shows:

Port 8080 • Waiting for DNS update

Things I have already tried:

  • Waiting more than an hour for DNS propagation
  • Re-adding the domain in Railway
  • Confirming nameservers are correct (Hostinger DNS)
  • Lowering TTL to 300

So it looks like DNS is resolving correctly, but Railway still isn't verifying the domain.

Would appreciate any help or suggestions on what might be causing the verification to fail.

Thanks!

Solved

1 Replies

Railway
BOT

3 months ago

Hostinger is listed in our docs as a DNS provider that does not support CNAME flattening or dynamic ALIAS records at the root level, which is why verification is not completing for your apex domain. The recommended workaround is to switch your domain's nameservers to Cloudflare (which does support CNAME flattening), as described in that same doc section, or use a subdomain like www.boldoai.in instead.


Status changed to Awaiting User Response Railway 3 months ago


Railway
BOT

2 months 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 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...