12 days ago
I set up a custom domain through GoDaddy and copied and pasted the DNS records into GoDaddy. But in Railway, the DNS records haven't updated, and it's been a week. I called GoDaddy support and they say my custom domain is pointed to Railway, but they say that the problem is that there are 3 "A" records (IP addresses?) for the custom domain. I didn't create any A records (wouldn't know how to do it), but GoDaddy says that I need to find out from Railway what the correct A record is and delete the other two in GoDaddy. How do I find out what the correct A record is supposed to be?
1 Replies
12 days ago
There is no correct A record for a Railway custom domain. We don't publish a fixed IP address, so all three A records on your root domain should go, and that is why the domain hasn't verified: we check for a CNAME pointing at the target shown in your service's Settings, Networking section, and none is in place. Your TXT verification record is already set up correctly.
A root domain like yours can't take a plain CNAME, so it needs a DNS provider that supports CNAME flattening or an ALIAS record. Our docs list GoDaddy as a provider that supports neither, so your root domain can't point at us while GoDaddy hosts its DNS.
You have two options. The first is to add www as the custom domain on your service instead, create the CNAME and TXT records it shows as ordinary records in GoDaddy, and use GoDaddy's forwarding to send the root domain to www. The second is to change the domain's nameservers to Cloudflare, as that docs page describes, and then add the CNAME at the root there.
Status changed to Awaiting User Response Railway • 12 days ago
5 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 5 days ago