Hi there,
I’m on the Pro plan and attempted to move my production domain website.com from GoDaddy to Railway. I would like help understanding why the custom domain did not validate or provision SSL when I pointed the DNS to Railway.

Here’s exactly what I did:

1. In Railway → Settings → Networking, I added two custom domains:

   • website.com

   • www.website.com

2. Railway provided CNAME instructions, but since GoDaddy does not allow CNAME records at the apex (@), I instead pointed my DNS A-records to the Static Outbound IP shown for my service:

   • A @ → 162.220.234.15

   • A www → 162.220.234.15

3. DNS propagated globally (confirmed via DNSChecker, all nodes resolved to 162.220.234.15).

4. After propagation, visiting https://website.com resulted in:
   ERR_QUIC_PROTOCOL_ERROR
   It appeared SSL never provisioned for the domain.

5. In Railway’s Networking tab, both domains continued to show:

   • “Waiting for DNS update”

   • “Incorrect DNS setup”

6. To restore service for my business, I reverted DNS back to GoDaddy hosting and everything came back online.

My Question

1. Can someone on the Railway team review my setup with me and guide me through the correct approach to cut over my domain?
   I want to ensure I’m following Railway best practices before attempting the migration again.

Extra Notes

• The React/Vite site runs perfectly at the Railway URL:
  https://website-production.up.railway.app/

• I did not alter any ports or service settings, only DNS.

• I am ready to retry the migration once I understand the correct configuration.

Thanks for your help!!

I appreciate any guidance on how to properly get a root domain working with Railway.