CNAME not connecting to Hostinger

Hello,

I can not figure out why my app on Railway can not connect to my Hostinger Domain. I have tried working with the Hostinger team and they said I needed to delete the A record and just use the CNAME you provided but it has been at least 4 days and nothing is working. Now they are saying I need to use an A record that points to Railway. I am so confused as I have another domain that is working just fine with no A record. Railway (you) host the Vite app and Hostinger hosts the domain. Any help would be appreciated.

Closed

6 Replies

a year ago

There is no cname set for @ on the domain. Please follow the instructions


Status changed to Awaiting User Response Railway about 1 year ago


Hi Jake,

Yes, the CNAME is attached, it has been for several days now which is why I am reaching out.


Status changed to Awaiting Railway Response Railway about 1 year ago


a year ago

There are no CNAMEs for the domain you have set on your service -

https://www.nslookup.io/domains/theshopsat550.com/dns-records/#google


Status changed to Awaiting User Response Railway about 1 year ago


OK, but I included screenshots in my last response indicating that it is. So, who do I debate this with now, and what are my next steps? Do I try deleting it on Railway and issuing a new one to point the CNAME to, or do I go back to arguing with them? I bought the domain less than 30 days ago, so I can not transfer it to another service.

Do I need to delete the URL you (Railway) produced that ends in production.up.railway.app?

I have been working on this for a week so please help me, don't just tell me to follow the directions (which I did and have an active setup for another app) or that I haven't set it when I include screenshots.

I like Railway, and I recommend it to others. Please actually help me, though.


Status changed to Awaiting Railway Response Railway about 1 year ago


a year ago

Per your screenshot you have the CNAME set on the www subdomain.

Yet you only have the root domain set on Railway.

Hopefully you can see the error here?

If you want to use the root domain with Railway, you will need to use Cloudflare's nameservers, they have a guide for that here -

https://developers.cloudflare.com/dns/zone-setups/full-setup/setup/

  1. Remove all DNS settings from Hostinger

  2. Remove all domains from Railway

  3. Switch to Cloudflare's nameservers

  4. Wait until Cloudflare says everything is setup correctly

  5. Set SSL/TLS to full - https://docs.railway.com/guides/public-networking#provider-specific-instructions

  6. Add your domain to Railway

  7. Add the given CNAME to Cloudflare

Note, this is nameserver change, not a domain transfer, the 30 day wait period is not applicable here.

Follow the steps here to a T and you will have a working domain, if the domain doesn't work, please re-do the steps.


Status changed to Awaiting User Response Railway about 1 year ago


Status changed to Solved leilanigreer 12 months ago


frankkode
HOBBY

a year ago

On Cloudflare Proxied will be enabled, or we will use DNS only i have the same issue


Status changed to Awaiting Railway Response Railway 11 months ago


Status changed to Closed brody 11 months ago


Loading...