a month ago
From the Railway Help Bot:
Send them this:
Subject: Custom domain DNS not resolving to correct service IP
I've set up a custom domain flights.ripcity.io pointing to my flights service via CNAME flights.ripcity.io.cname.railway.app.
The CNAME is configured correctly at my registrar, but it's resolving to the wrong IP:
flights.ripcity.io.cname.railway.appresolves to34.107.141.139ripcity.up.railway.app(the default Railway domain) resolves to151.101.2.15
The custom domain doesn't work in the browser, but the default Railway domain works fine. The DNS is pointing to a different IP than the actual service.
Project ID: 01163cda-ece6-4e7d-af69-abb268a11276
Environment: production
Service: flights
Can you investigate why the custom domain CNAME is routing to a different IP?
That gives them all the concrete data they need to debug it.
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open Railway • about 1 month ago
a month ago
The CNAME should look something like 802xaqix.up.railway.app. Are you sure that's the CNAME Railway provided for you to add to your DNS records?