dont believe so, https://docs.railway.com/guides/public-networking

even on enterprise?

hmmm that makes it very tricky

to shard traffic

unfortunate

idk about enterprise tho, i use a pro plan

idk if theyd make exceptions or stuff for enterprise

route53 is what we use

i think in all of them it asks you to swap to CF

too risky to do that for us

thanks for chiming in moe!

i get that, hopefully one of the employees might know something more than we do

<:sadcat3:1268043255153688708>

appreciate it <:ChromaHandshake:1207743165440983150>

By shard you mean a Load Balancer?

Also, we highly recommend Cloudflare if possible, as it provides DDoS protection.

Empoeye here. We don't currently offer anything other than CNAMEs, regardless of plans.

We know CNAMEs only can be limiting, and we do want to offer A types at some point in the future, but we do not currently have any plans for that.

So yes, we would highly recommend Cloudflare. They provide a seamless DNS record import, and they provide a WAF and DDoS protection.

team is quite apprehensive to do so

due to latest cloudflare stuff

You have a point there.

also the risk of having downtime while switching domains

and we have a lot right now

If you really do not want to depend on Cloudflare then you can use DNS only (Cloudflare won't proxy it)

im thinking what can be a way forward <:think:1169350591718379670>

That, or use a subdomain.

walk me through this so current setup is

subdomain.domain has A and AAAA record pointed to cloudfront (Route 53)

what i have tried:

make those records weighted records

and add A record for railway (ipv4)

but cert errors occur

CNAME support for subdomains is standard and supported by any registry.

oh

so you're telling me i can actually put a cname record for subdomain.domain

subdomain.domain.com - yes

gotcha, i kept being told it won't work by claude

but i shall try within the day and report back

also cool that discord help threads are more responsive than slack HAHAHA

i will just keep asking here <:salute:998553677432356876>

Oh wow, I am surprised Claude is trying to gaslight you on this topic. CNAMEs for subdomains have always been supported; it's CNAMEs on the apex or root domain that is the issue.

examples of gaslight

Slack threads are only answered by railway employees who work off a queue in the central station with all other users' threads. On Discord, you get the community, so for anything that the community is able to answer, asking in Discord would definitely get a faster response, for the most part.

hooray discord HAHAHA

It's true, as long as that sentence is in the context of a root domain.

yeah but here i clearly showed a screenshot of our route53 routes

showing api2.domain.com

haha

anw thanks Brody!

hope i land this railway migration properly aaaaaaaa

We hope you do too!

so to clarify

given existing

a and aaaa subdomain pointing to cloudfront (Weighted routing 90)

ill just add

cname record for subdomain pointing to railway (Weighted routing 10)

that's pretty much it right

okay so it's really not possible though cc @Brody

Yeah you can't mix and match, but a CNAME would be supported otherwise.

what would u suggest to move forward

because testing safely is really a non negotiable

Even if route 53 allowed that, it wouldn't work for us to verify your domain, because what are the chances our backend gets a DNS result routed through to Railway, it would likely be routed to your infra and then fail the validation.

gotcha

so hmmm

You may have to move away from a DNS based load balancer

what are the options

i was thinking maybe just shard traffic in the caller side (application)

but that seems very iffy

I am not too familiar with AWS but surely they offer a L7 load balancer that you could do weights with?

the L7 load balancer

(ALB)

only points to aws resources

so cannot route to external stuff like railway

A really bad workaround but maybe he could use Cloudflare SaaS?

Basically you could create a Cloudflare account, add any domain and then use Cloudflare SaaS to add your domain from Route53
That will require a Cloudflare Pro accont though, and as plus you'll get Cloudflare DDoS protection.

Let me confirm if it's possible as I don't remember if Cloudflare SaaS generates a A domain or CNAME domain

im quite stressed about this but last solution im looking at is

lambda assosciation in cloudfront at origin request, so can rewrite the host and match railway?

and then inside the lambda some random stuff to decide whether or not to go to same origin (the normal alb) or go to railway

Nevermind, it uses CNAME