Confirm DNS setup: Root domain CNAME causing email conflict
seifui
HOBBYOP

6 months ago

Hi,

I’m having an email delivery issue caused by my current DNS setup.

My domain has a CNAME record on the root domain (@) pointing to Railway. Namecheap confirmed that this CNAME overrides MX records and breaks email delivery.

To resolve this, I need to:

  • Replace the root-domain CNAME with an ALIAS or A record, or
  • Move the CNAME to www and use a different record type for the root domain.

Could you please confirm:

  1. Whether Railway supports ALIAS records for root domains
  2. If not, which A record IP(s) I should use instead
  3. Your recommended DNS configuration to avoid email conflicts while keeping Railway hosting

Thanks for your support.

Solved$10 Bounty

Pinned Solution

I would suggest using Cloudflare's DNS. Other DNS providers may not provide full flattening features.

I have several MX and CNAME records on my root domain and everything works just fine.

To answer your questions:

  1. You need to use CNAME records for custom domains with Railway
  2. Railway does not provide A records for custom domains
  3. Cloudflare DNS is recommended

2 Replies

I would suggest using Cloudflare's DNS. Other DNS providers may not provide full flattening features.

I have several MX and CNAME records on my root domain and everything works just fine.

To answer your questions:

  1. You need to use CNAME records for custom domains with Railway
  2. Railway does not provide A records for custom domains
  3. Cloudflare DNS is recommended

0x5b62656e5d

I would suggest using Cloudflare's DNS. Other DNS providers may not provide full flattening features. I have several MX and CNAME records on my root domain and everything works just fine. To answer your questions: 1. You need to use CNAME records for custom domains with Railway 2. Railway does not provide A records for custom domains 3. Cloudflare DNS is recommended

seifui
HOBBYOP

6 months ago

I will try this. Thank you very much!


Status changed to Solved noahd 4 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...