Env name in private network domain
Anonymous
FREEOP

2 months ago

Currently, railway generates 2 private domains for each service

First domain is:

{service-name}.railway.internal

Second one is:

{service-name}

It would be nice to have a third domain in this format:

{service-name}.{environment}.railway.internal

The reason:

Because all environments in railway get the same subnet mask. So if i have tailscale setup, i would resolve {service-name}.railway.internal to 2 IPs. Which means you cannot access a specific one environment if you want, your system DNS resolver would load balance in the best case scenario. Which is not what we want.

Under Review

0 Threads mention this feature

0 Replies

Loading...