Railway DNS dilemma

alexjs-dev
HOBBY

a year ago

Hello,

I have a domain: urly.ws, I need my railway app to be accesibile for
https://urly.ws

What Railway suggests is that I update my DNS records with:

CNAME - @ - n9lo7u7O.up.railway.app.

Now, all of that is fine, unless you decide that you want to have emails, I've been fighting with protonmail for the past 2 days, only to find out that

"there is also a CNAME record with the hostname as @, A CNAME record to a bare domain will suppress all other records including the mail records." - Namecheap customer support

Meaning IF you decide to use your root domain with RAILWAY, it's impossible for you to also have emails with the same domain.

Any way I could solve this issue?

6 Replies

a year ago

Use cloudflare's CNAME flattening with their proxy, that way you won't have a CNAME at the root, you would end up with an A record at the root.


alexjs-dev
HOBBY

a year ago

Use cloudflare's CNAME flattening with their proxy, that way you won't have a CNAME at the root, you would end up with an A record at the root.

Ehh.. Sadly Cloudflare doesn't support "ws" domain extension, and other DNS providers can be costly.


a year ago

You might not be able to buy a .ws domain from them, but you can definitely use their nameservers with a .ws domain, same goes for .app domains, and that's exactly what Railway does, railway.app is registered with namecheap but DNS is managed by cloudflare.


alexjs-dev
HOBBY

a year ago

🧠🧠🧠
Thank you 🙏


a year ago

Let me know if that works out!


a year ago

Hi.
I've registered my domain by inserting the CNAME that Railway indicates, but I still can't access the site.

That is, my site is not yet public, even though I set it that way.

On the other hand, I haven't been able to do the deploy, I always get: Deployment Failed during process