3af4eb75-c9f3-4675-b813-0f3f3fc2b190

I am also in need of this for 1f7cc3a8-76f3-47c2-beba-2b5bb6e4e202

For context^

Running a dig against the CNAME domain the setup instructions gives me (e.g. [something.up.railway.app](something.up.railway.app)) yields this: ```❯❯ dig qt0utsxf.up.railway.app

; <<>> DiG 9.10.6 <<>> qt0utsxf.up.railway.app
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12971
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;qt0utsxf.up.railway.app. IN A

;; ANSWER SECTION:
qt0utsxf.up.railway.app. 60 IN CNAME edge.railway.app.
edge.railway.app. 300 IN A 66.33.22.2
edge.railway.app. 300 IN A 66.33.22.1
edge.railway.app. 300 IN A 66.33.22.4
edge.railway.app. 300 IN A 66.33.22.3

;; Query time: 33 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Sun Apr 06 18:16:05 EDT 2025
;; MSG SIZE rcvd: 135```

I'm going to test my app with those 66.33.22.* IPs as @ A records and see if that works

Unclear if they are static IPs, but that fact that [edge.railway.app](edge.railway.app) has A records to four of them seems promising

Aaaaand that does not work, yields an error due to the certificate not matching the domain

I've been loving Railway, but unfortunately if this is not possible I will need to switch providers.

This is a pretty huge restriction for anything other than hobby apps -- a little upset that "Custom Domain Support" is marketed when it's not actually supported fully.

Are you sure it's not fully supported? That would be pretty insane, that means you can't even have a custom email address if the root domain is hosted on railway

Their docs say it isn't supported https://docs.railway.com/guides/public-networking#adding-a-custom-domain

They support CNAME flattening and ALIAS records, otherwise the docs say (unhelpfully) "just change your name servers!"

Oh, can't we just use ALIAS then?

That would enable us to use TXT records

You can if your DNS provider supports it

I'm not going to switch my DNS provider just because a PAAS product decided to not support the most straightforward DNS mechanism for domain redirection

The problem is that all the mechanisms Railway supports (CNAME flattening, ALIAS records) are not standard DNS features

So they are not guaranteed to work with all services.

Ah I see

That's so irritating

Thanks

!s