a month ago
I'm trying to add a custom domain for client.mydomain.com and the cname given to me is @ which is incorrect? If I use clients.mydomain.com I get the clients cname as I'd expect. I also tried using client.mydomain.com and setting the name values to what I think they should have been (client and _railway-verify.client) but that didn't seem to work for me (where as someone in the linked support thread had said it worked for them).
Note that I have another service with a custom domain that already uses the @ cname for my domain so I can't reuse it with the client subdomain. Also, I can't simply change the subdomain from client to clients because I'm moving from a vps to railway and this service already has production traffic.
See: https://station.railway.com/questions/custom-domain-shows-wrong-cname-record-da7242f8#qzd7
Pinned Solution
a month ago
Ignore what Railway shows for the name. In your DNS provider manually set:
CNAME name: client → value: xxxx.up.railway.app
TXT name: _railway-verify.client → value: the verify string from Railway
You said you tried this and got "connection not private" — that's an SSL provisioning timing issue, not a DNS mistake. After setting those records, remove the domain from Railway and re-add it to trigger a fresh cert attempt once DNS has propagated.
Also i tryed to redo you're steps and got the same bug and the only thing that worked for me was removing the service and ading it back after that..
8 Replies
a month ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 29 days ago
a month ago
Try removing the domain from Railway, reload the window, and add it back.
0x5b62656e5d
Try removing the domain from Railway, reload the window, and add it back.
a month ago
I tried that a few times, no dice.
a month ago
If client.mydomain.com is pointing to your VPS's IP address via an A or AAAA record, I suggest you delete it, then remove your domain from Railway and add it again. If it still gives you @ for the CNAME, try to manually add client regardless as you suggested.
darseen
If `client.mydomain.com` is pointing to your VPS's IP address via an `A` or `AAAA` record, I suggest you delete it, then remove your domain from Railway and add it again. If it still gives you `@` for the `CNAME`, try to manually add `client` regardless as you suggested.
a month ago
Ok, I'll give that a shot outside of business hours tonight and report back on the results.
darseen
If `client.mydomain.com` is pointing to your VPS's IP address via an `A` or `AAAA` record, I suggest you delete it, then remove your domain from Railway and add it again. If it still gives you `@` for the `CNAME`, try to manually add `client` regardless as you suggested.
a month ago
Ok I finally was able to try this out, still no dice. I removed the cname that was set previously (to a non-railway host), then tried adding the custom domain and I'm observing the same behavior. I tried adding the client cname and txt record and after doing that I can't get past "This connection is not private".
a month ago
Ignore what Railway shows for the name. In your DNS provider manually set:
CNAME name: client → value: xxxx.up.railway.app
TXT name: _railway-verify.client → value: the verify string from Railway
You said you tried this and got "connection not private" — that's an SSL provisioning timing issue, not a DNS mistake. After setting those records, remove the domain from Railway and re-add it to trigger a fresh cert attempt once DNS has propagated.
Also i tryed to redo you're steps and got the same bug and the only thing that worked for me was removing the service and ading it back after that..
a month ago
Yeah I think you're right, I removed it again and re-added making sure to refresh the browser each time and it's resolving for me now (confirmed via the http logs) even though the railway ui still says the dns isn't setup properly.
--edit--
That eventually resolved itself as well so I think I'm good. Thanks again @pagetree
atseanwash
Yeah I think you're right, I removed it again and re-added making sure to refresh the browser each time and it's resolving for me now (confirmed via the http logs) even though the railway ui still says the dns isn't setup properly. --edit-- That eventually resolved itself as well so I think I'm good. Thanks again @pagetree
a month ago
yo uare most welcome sir! glad i could help :)
Status changed to Solved passos • 24 days ago