9 days ago
We are currently facing an issue where our Railway-hosted backend is not accessible in certain networks—likely due to ISP-level DNS restrictions. Based on my research, this seems to be unrelated to Railway’s configuration.
To work around this, we are planning to use a custom domain.
We have already purchased a root domain from GoDaddy, and our plan is to create a subdomain (e.g., api.ourdomain.com) and configure a CNAME record pointing to our Railway app’s public URL.
question is:
Since GoDaddy doesn’t support root-level CNAMEs, will using a subdomain with a proper CNAME setup from GoDaddy be sufficient to resolve this DNS access issue in restricted regions? Or will we still face compatibility problems with Railway unless we switch to Cloudflare?
5 Replies
9 days ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
8 days ago
Using only Cloudflare to make it work is not true. You can still proceed with GoDaddy's subdomain to get it resolved. I have already set up a custom domain (in Hostinger) and it is working fine for every region.
Note: Always use a subdomain for the custom domains, because if not used, then your main domain will always point to the railway-hosted service, which no one wants (and no cloud provider allows you to tell the root-level domain to other services)
Follow these steps:
a. Make sure that you map the correct port to the custom domain while configuring it.
b. Once it says that "the domain is available", you can click the add button.
c. Then it will show you the CNAME that has to be added for the subdomain (in your case).
d. Then open your GoDaddy settings, where you can DNS settings (something like DNS Zone Editor, under the Advanced settings).
Ensure that you choose 'CNAME' as the type in the editor, and the name will be the subdomain name, along with the value pointing to the railway servers.
NOTE: Before adding this CNAME property for the subdomain, ensure that there are no "A/AAA/CNAME" DNS values set for it, unless the new one is to be added. Delete the already existing entries for the subdomain, and then add what is shown in the Railway dashboard.
Then, after a couple of minutes, the subdomain would be verified, which would be shown by the tick inside the service's networking settings.
Note that the DNS take about 72 hours to affect each region. So, initially, when it is verified, you won't be able to see the railway server results when you open the custom domain link (as it still uses the https/http port number 443/80), and your railway service must be listening to any other port mentioned by you in the code file.
So, to test whether the same has been updated or not, you can do a fetch request from POSTMAN to your custom-domain URL, as it uses your defined port only.
I hope that helps you 
clashing
Using only Cloudflare to make it work is not true. You can still proceed with GoDaddy's subdomain to get it resolved. I have already set up a custom domain (in Hostinger) and it is working fine for every region.Note: Always use a subdomain for the custom domains, because if not used, then your main domain will always point to the railway-hosted service, which no one wants (and no cloud provider allows you to tell the root-level domain to other services)Follow these steps:a. Make sure that you map the correct port to the custom domain while configuring it.b. Once it says that "the domain is available", you can click the add button.c. Then it will show you the CNAME that has to be added for the subdomain (in your case).d. Then open your GoDaddy settings, where you can DNS settings (something like DNS Zone Editor, under the Advanced settings).Ensure that you choose 'CNAME' as the type in the editor, and the name will be the subdomain name, along with the value pointing to the railway servers.NOTE: Before adding this CNAME property for the subdomain, ensure that there are no "A/AAA/CNAME" DNS values set for it, unless the new one is to be added. Delete the already existing entries for the subdomain, and then add what is shown in the Railway dashboard.Then, after a couple of minutes, the subdomain would be verified, which would be shown by the tick inside the service's networking settings.Note that the DNS take about 72 hours to affect each region. So, initially, when it is verified, you won't be able to see the railway server results when you open the custom domain link (as it still uses the https/http port number 443/80), and your railway service must be listening to any other port mentioned by you in the code file.So, to test whether the same has been updated or not, you can do a fetch request from POSTMAN to your custom-domain URL, as it uses your defined port only.I hope that helps you
8 days ago
Do let me know if you have any issues
4 days ago
Any update, richujomy
clashing
Using only Cloudflare to make it work is not true. You can still proceed with GoDaddy's subdomain to get it resolved. I have already set up a custom domain (in Hostinger) and it is working fine for every region.Note: Always use a subdomain for the custom domains, because if not used, then your main domain will always point to the railway-hosted service, which no one wants (and no cloud provider allows you to tell the root-level domain to other services)Follow these steps:a. Make sure that you map the correct port to the custom domain while configuring it.b. Once it says that "the domain is available", you can click the add button.c. Then it will show you the CNAME that has to be added for the subdomain (in your case).d. Then open your GoDaddy settings, where you can DNS settings (something like DNS Zone Editor, under the Advanced settings).Ensure that you choose 'CNAME' as the type in the editor, and the name will be the subdomain name, along with the value pointing to the railway servers.NOTE: Before adding this CNAME property for the subdomain, ensure that there are no "A/AAA/CNAME" DNS values set for it, unless the new one is to be added. Delete the already existing entries for the subdomain, and then add what is shown in the Railway dashboard.Then, after a couple of minutes, the subdomain would be verified, which would be shown by the tick inside the service's networking settings.Note that the DNS take about 72 hours to affect each region. So, initially, when it is verified, you won't be able to see the railway server results when you open the custom domain link (as it still uses the https/http port number 443/80), and your railway service must be listening to any other port mentioned by you in the code file.So, to test whether the same has been updated or not, you can do a fetch request from POSTMAN to your custom-domain URL, as it uses your defined port only.I hope that helps you
8 hours ago
richujomy, did that helped