13 days ago
I am trying to connect my custom domain (woodstylejoinery.co.uk) to my Railway deployment.
Railway has provided the following DNS records:
- CNAME @ → xxx.up.railway.app
- TXT _railway-verify → [verification value]
- CNAME www → xxx.up.railway.app
- TXT _railway-verify.www → [verification value]
The www subdomain is working correctly, and the TXT verification records have been added successfully.
However, my Client's DNS provider (Fasthosts) does not appear to allow a CNAME record on the root domain (@), so I cannot add:
@ → ca6yl75m.up.railway.app
Cloudflare handles this configuration without issue via CNAME flattening, but I sadly cannot get my client to move to cloudflare due to the fact the DNS entry is managed externally.
What is the recommended approach for connecting the apex/root domain when the DNS provider does not support root-level CNAME records? Does Railway provide A records, support ALIAS/ANAME records, or recommend a different configuration?
Any guidance would be appreciated.
1 Replies
13 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 13 days ago
13 days ago
Railway does support dynamic ALIAS records at the root domain. If neither CNAME flattening nor dynamic ALIAS records are supported by your DNS provider, your only option is to change your domain's nameservers to point to Cloudflare's nameservers.
You can read more about this here: https://docs.railway.com/networking/domains/working-with-domains#adding-a-root-domain