49c5f0bc-621a-4388-8576-9a3edb59e080

that register does not support root level cnames, you will need to use cloudflare's nameservers.
cloudflare has a guide for that here -

Do you know of any other site where you can buy a domain to use Railway data there?

you dont need to buy a new domain, im not sure how you got that out of what i said, you simply need to use cloudflare's nameservers

Got it, I'll try to figure it out. Thank you

read cloudflare's guide

I did everything according to the guide you gave, updating servernames for my domain on the registrar's site. Now I need to connect the data from railway to cloudflare?

I'm not sure where you got those IP addresses from but railway does not use IPs for anything, remove them and replace them with the CNAME you got from Railway

so?

if that's the CNAME railway gave you, yep

Yes, that's the data Railway gave me.

Should it be something like this? Or will the status also change, for example to "Active"?

you are using a cloudflare proxy so that status is correct

within cloudflare go and set your SSL/TLS settings to "Full"

done

does it work?

yea

thanks you

no problem!

I have another small question, how can I add subdomains?

the same way you added the root domain

Something like that?

not quite

• Name refers to just the subdomain (or @ for the root)

• that's the same target as you've used previously, you need to add another domain to your service to get another CNAME

• you'll likely want to have the API subdomain on a different railway service

Got it, I need that last point

This requires bringing up another service or can be done like this:

yes, add another service to the project and deploy your backend, it would make no sense to have an api subdomain on the service that serves your frontend

Yes, I understand that it needs to be connected to a servlet that provides the backend, but this is a test site, so I'd like to learn as much as possible

test or not it would make no sense to have an api subdomain on the service that serves the frontend

Just if the backend is on a different domain, but I want to have a subdomain, do I have to specify it in the Networking section or do I need a new service for each subdomain?

the backend does not need to be on a different domain, use a subdomain on another service

you do not need a new service for each subdomain, but like I said it makes no sense to have the api subdomain on the service that serves your frontend, create another service for the backend and add the api subdomain to that service

Yeah, that's what I meant. Thank you for explaining it so thoroughly

<:1010:1173874936306221126>