I used another DNS checkup tool and couldn't see any CNAMEs on mlconfessions.com, it's worth noting that hostinger doesn't support root level CNAMEs anyway so if that's what you're trying to add then you might need to use Cloudflare as nameserver instead

Regarding the domain being stuck on "Issuing TLS certificate", could you try removing the domain from Railway and remove the CNAME from your DNS, then finally add them back?

No, I am not using a root-level name change, as you can see in the screenshot below. Is everything correct as shown? Based on your suggestion, I deleted and re-added them in both places. Railway provided a different URL than the one shown in the image. So I added new url in dns records:

New URL: 2k14dee0.up.railway.app

Is everything set up correctly?
and how long it takes to generate TLS certificate? Is it dependent on railway or dns propagation?

Not quite, you need to use a CNAME and not an ALIAS record*
so you'd want to do CNAME with a name of www and content, in this case, of 2k14dee0.up.railway.app

If it needs to be on the root of the domain and not on a subdomain like www then I'd advise using Cloudflare as a nameserver instead, which then allows you to add CNAME records on the root of your domain

(Note: You might need to repeat the process considering it has passed to TLS issuance)

* ALIAS records do sometimes work but it's highly dependent on whether the nameserver you're using resolves the record dynamically, I'm not 100% sure if this is the case with Hostinger, I still adivse using Cloudflare as a nameserver since it removes any doubt

I did add as a CNAME record but hostinger automatically add as ALIAS record. I would prefer to avoid using Cloudflare in early stages.
I am fine with redirecting. If I understand correctly, CNAME www would redirect to mlconfessions.com and then ALIAS @ would redirect to 2k14dee0.up.railway.app

As you had said earlier hostinger doesnt allow adding CNAME records so I think my settings are correct. is it?
what do you recommend? do I need to update CNAME record in the hosting which means replace mlconfessions.com with 2k14dee0.up.railway.app ?

Below updated settings

Also when I added custom domain on railway networking, it showed to add
CNAME @ record with the 2k14dee0.up.railway.app
If I go by your suggestion, you are suggesting to use CNAME www record with 2k14dee0.up.railway.app
So my question is, is adding CNAME with www record correct? Will my site work?
Is TLS certificate dependent on railway or dns propagation?

Sorry for my confusion, I've never used Hostinger so I'm not entirely certain of how it handles DNS records, although my intuition tells me your setup is incorrect. I believe it's creating the ALIAS record automatically because you're trying to apply a CNAME on the root which you can't do in Hostinger, and Hostinger is likely handling that the best it can by creating the ALIAS record.

To clarify when I say you should use Cloudflare as nameserver, I'm not saying you need to proxy through Cloudflare, only that you use Cloudflare to handle your DNS records. That way you can receive requests on mlconfessions.com (the root domain)

I did now find out Hostinger does not have dynamic ALIAS records, so this setup wouldn't work at all and the only way you'll be able to use the root domain would be to use Cloudflare as a nameserver.

Also, yes you're right it wouldn't work to use a www CNAME unless you also have that setup on Railway, forgot to add that. It's the only other alternative if you really do not want to use Cloudflare as a nameserver.

I also came across adding ip address for the deployed service for the custom domain.
Can I do that?

No you cannot.

Hostinger does not support root level CNAMEs.

Therefore, you need to use Cloudflare, and you need to use a CNAME.

I have switched to cloudflare nameservers.

I had to remove below two entries from cloudflare DNS management as I could not add CNAME records.

A	@	0	84.32.84.32	
CNAME www	0	mlconfessions.com 

I replaced above entries with



I had followed this link till step 3
https://docs.railway.app/guides/public-networking#adding-a-root-domain-with-www-subdomain-to-cloudflare

I still have a hunch that my settings are not correct.
Now can you confirm if my settings are correct or can you also point out references for adding it correctly? Any help would be highly appreciated

Please see these docs now - https://docs.railway.app/guides/public-networking#provider-specific-instructions

Highly appreciate this velocity, guys! Thank you! Will go over this doc

Guys your understanding of Hostinger not providing root level CNAME is completely wrong. I have created the service with another domain and setup the root and sub domain in the networking and made the corresponding changes in hostinger.
The only difference is, I added both domains with CNAME and removed A entry from dns records and both domains were setup on railway networking as well.

Hostinger does not support CNAMEs at the root, they support ALIAS types, and that's not the same, nor is it something we support long term, despite it "working" for now.

Okay. Thank you for the clarification.
One more thing, below dns check is failing for the root domain, but the website is working. Any idea why this might be the case? I removed A records from cloudflare as well. Is that fine?
https://www.whatsmydns.net/#CNAME/mlconfessions.com
and while subdomain is showing the changes
https://www.whatsmydns.net/#CNAME/www.mlconfessions.com

pls explain

Because there is technically no CNAME at the root right now, you have Cloudflare proxying turned on (the orange cloud) so Cloudflare replaces the CNAME at the root with an IP address, an IP address for Cloudflare's servers so your traffic flows through their proxy.

Unless you have a very specific reason to turn it off, we recommend you keep it on.

Okay. what is the right way? should I enable the proxystatus or use DNS only? Are there any disadvantages or advantages using proxying turned on?
pardon my noob question.

Yes please keep the proxy enabled (orange cloud)

As for why you want it on, it would allow you to have TXT and MX records also at the root, even if you don't need this, it's best to leave the proxy enabled.