a month ago
Hi Railway support,
We have two custom domains configured on our frontend service that are not resolving despite correct DNS setup. Requesting manual intervention.
Project ID: 5c6497c1
Service: Reel Africa Frontend (ID: 68ee2be4)
Environment: production (ID: 7c876b4e)
Domains: reelafrika.africa and reelafrika.co.za
What we've done:
Both domains are added to the Railway frontend service
Our DNS registrar (domains.co.za) has confirmed DNS is updated and propagated — confirmed in writing today 26 May 2026 by their support agent JP C
Railway CLI confirms both domains are listed on the service
The frontend is live and accessible via the Railway internal URL: https://reel-africa-frontend-production.up.railway.app
Current DNS state:
reelafrika.africa — returns no DNS records at all (NXDOMAIN)
reelafrika.co.za — resolves to 66.33.22.192 (appears to be a stale A record, not our CNAME)
What we need:
Confirmation of the exact CNAME value Railway expects for each domain (from the dashboard)
Whether a TXT verification record is also required and what its value should be
If Railway's edge is holding a stale record — please force re-verification and SSL provisioning for both domains
The app is production-ready and sitting behind dead domain names. Any assistance to unblock this urgently appreciated.
Railway CLI version: 4.62.0
Account: vanderberg.henry@gmail.com
Thank you.
Pinned Solution
a month ago
Railway’s dashboard will tell you the exact CNAME and TXT records to add to your DNS provider. Additionally, it may take up to a few hours (maybe even a day, but rarely), for Railway to validate the DNS and issue certificates. If it doesn’t happen by then, try removing the domain from Railway and add it back after ~10-15 mins.
You also need a TXT records on _railway-verify.reelafrika.africa.
2 Replies
Status changed to Open Railway • 29 days ago
a month ago
Railway’s dashboard will tell you the exact CNAME and TXT records to add to your DNS provider. Additionally, it may take up to a few hours (maybe even a day, but rarely), for Railway to validate the DNS and issue certificates. If it doesn’t happen by then, try removing the domain from Railway and add it back after ~10-15 mins.
You also need a TXT records on _railway-verify.reelafrika.africa.
a month ago
NXDOMAIN for reelafrika.africa means your registrar hasn't actually published the records yet, regardless of what their support agent told you. their authoritative nameservers are returning nothing for the hostname.
verify directly against their NS, not your local resolver:
dig NS reelafrika.africa(get the authoritative nameservers)dig CNAME reelafrika.africa @<that NS>(query them directly)
if the direct-NS query returns nothing, the records aren't live. push back on domains.co.za to confirm the zone actually contains the CNAMEs you specified.
reelafrika.co.za resolving to 66.33.22.192 is an A record, not a CNAME. delete the A record — railway needs the CNAME (alias to xxx.up.railway.app), not an A.
once both domains return the correct CNAME from their authoritative NS, the _railway-verify TXTs ben mentioned will validate too. you need both records per domain: CNAME for traffic, TXT for ownership.
Status changed to Solved 0x5b62656e5d • 4 days ago