You should also be adding your root domain if you wish to use www.

Keep in mind that some DNS providers don't support CNAME flattening, so if that's the case, I'd recommend switching to Cloudflare DNS.

"I have already added www.liavo.fr to the precious-comfort service. Should I also add the root domain liavo.fr (without www) as a separate custom domain on the same service? And regarding Cloudflare DNS — my DNS is managed by OVH, not Cloudflare. Would switching DNS management to Cloudflare fix the CNAME flattening issue?"

Yes. You shold add liavo.fr.

Would switching DNS management to Cloudflare fix the CNAME flattening issue?

I wouldn't say "fix." This just allows you to use a CNAME record on a root domain if your current DNS provider doesn't allow it.

Thanks Pepper, Added liavo.fr as second custom domain. Both liavo.fr (A record 66.33.22.1) and www.liavo.fr (CNAME cuu4wdo1.up.railway.app) are fully propagated via Google DNS. Both domains still show 'Waiting for DNS update' in Railway dashboard. SSL never generates. Can someone from the team manually trigger SSL provisioning for both domains on service precious-comfort, project 68313907-c9fc-4ddc-9535-3a6a642e6e3c?

Railway doesn't support custom domains with A name, if you wish to use the root domain on Railway you must use a DNS provider with CNAME flattening (Cloudflare)

Can you confirm that the CNAME value matches what Railway shows when you press on "Cloudflare proxy detected" or "DNS records"?

Yes, I'm switching to Cloudflare DNS right now. Nameserver propagation is in progress. The CNAME value for both www.liavo.fr and liavo.fr is cuu4wdo1.up.railway.app — DNS only, no proxy. I'll confirm once Cloudflare is fully active

Each custom domain gets its own CNAME value

www.liavo.fr and liavo.fr are 2 separate domains, they get a value each

Updated the CNAME for liavo.fr to p7metf7f.up.railway.app. Waiting for propagation.

Could you also screenshot the public networking section in service settings?

Make sure to add TXT records if instructed to.

Did you add the TXT records as instructed?

Both TXT records are already added in Cloudflare — railway-verify=bd87eeffb1... and railway-verify=2fc3d94c0... both DNS only.

You need the underscore.

Confirmed. Both TXT records match exactly what Railway shows in DNS records for each domain

Did you add the _railway-verify (and _railway-verify.www)?

I nslookup-ed it and it seems like you only added the TXT records to @.

Added _railway-verify TXT with value for liavo.fr, and _railway-verify.www TXT with value for www.liavo.fr. Both DNS only in Cloudflare. Nameservers are igor and rafe.ns.cloudflare.com ; propagation confirmed by OVH but Cloudflare still verifying. Should be active within the hour.

should be able to remove these

Railway should detect the DNS changes soon.

okkkk thank's, liavo.fr is online