I have already set up a custom domain, 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), and it poses issues in doing so (which is happening in your case)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

I have already set up a custom domain, 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), and it poses issues in doing so (which is happening in your case)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

thank you