CNAME vs ALIAS
My DNS provider doesn't allow CNAME for the @ root of the domain, only ALIAS.
Can I use ALIAS?
13 Replies
Project ID:
d1c85c02-8ca5-43c3-adc6-4a24cb066e33d1c85c02-8ca5-43c3-adc6-4a24cb066e33
Technically, you can as CNAME and Alias records achieve the same result.
But I don't think railway has an option to choose anything other than CNAME to verify. I would suggest you a DNS proxy like Cloudlfare for your domain. Its free and quick to setup.
I don’t want to use Cloudflare ideally 💀
Previously was working fine with ALIAS
Has something changed with Railway domains?
It seems reachable
But I don’t know for sure…
oh if it used to, then try it. it might resolve then.
I use DNSimple to manage the domain by an API
There’s some things I’ll be doing soon to separate tenants in the api by domain name
I am very little knowledge about multitenancy, but wouldn't each domain have its own DNS records accessible through the API? so you can assign services based on the unique domain name anyway, isn't it?
Yeah I do a bunch of stuff for like mail forwarding etc, DNSimple is really good for a programmable interface for DNS
I’m happy not to use Cloudflare for the moment
I had not heard of it before, looks cool and much simpler to manage.
Yeah 🚀
as I understand it, an alias record will resolve the cname address once, so as long as the IP address for that cname record doesn't change everything works, but then you push a code change, you get placed on a different box, your IP changes, then the IP your domain points to is incorrect and everything breaks
just read this https://support.dnsimple.com/articles/alias-record/
it looks like, unlike other DNS providers, dns simple will resolve the record dynamically, so it should work by all means
@Brody you're a legend thankyou
Solution
sounds basically like what cloudflare does to allow cnames at the root