2 years ago
Hello,
one of my project services lost its connected domain in public network settings. The domain is maintained via Cloudflare, a subdomain entry which is used by the service is created, the required CNAME record exists since months. Everything was working fine until now, today Railway lost the connection and says that the CNAME record has not been found yet.
I don´t know what happened because I haven´t changed anything. Do you have any advice? Is it maybe an issue on Railway?
Thanks in advance.
Regards,
Marco
32 Replies
2 years ago
Interesting, do you mind sharing some screenshots of the services public networking and your DNS settings in cloudflare?
Attached you will see the settings at the service and a copy of the DNS setting in Cloudflare.
2 years ago
does the domain work?
2 years ago
very odd, can you remove the domain from the service and add it right back, but don't touch anything in cloudflare
but it will mean that I will have to update the CNAME entry at Cloudflare, because the record value has changed on Railway side then.
2 years ago
you would not need to, that value is completely random and only serves as a means for cloudflare to resolve an IP address
this hasnt changed anything except that I should update the CNAME to the new value now. 😉
2 years ago
it will tell you to do that, but you don't strictly need to
2 years ago
what is this MIT proxy? and how does it differ from what that button normally says?
Have tried disabling, but hasnt changed anything as well. Or maybe I am not patient enough.
2 years ago
Right but why does it say MIT proxy, I haven't seen the MIT part of that ever
Cloudflare uses that proxy to route it threw their firewall if proxy is enabled I guess.
2 years ago
I get that but yours says "MiT Proxy" mine just say "Proxied"
Ahh, yeah its just because of the language… in german it says "mit proxy" which is in english language "proxied" i guess.
2 years ago
okay that makes sense, sorry for the confusion
2 years ago
would you happen to have any other records on that subdomain?
Ok, maybe I have found the issue. If its the reason then it wasn´t a problem at your side. Seems like the NS settings have changed. Currently figuring out why it happened.
Since I am sure that this was the reason I would suggest that I will write again once I have any results from it.
It was the reason. Sorry for the inconvenience!
The post can be closed now. Seems like the original host (IONOS) has changed the NS settings to default and so Cloudflare wasn´t responsible for the domain anymore.
Status changed to Solved Railway • almost 2 years ago
2 years ago
Ah that is incredibly odd, thank you for letting me know the root cause, now I'll have some additional insights into this issue if someone ever opens a similar issue in the future!
Something I never would´ve thought on my own - needed our discussion to let me have a view on it.
Thank you for your help and patience.
2 years ago
Got same problem right now with one of my services. I'll check if my domain registar is working, mb namecheap changed something too.
Looks suspicious, because i've got problem at the same time as tribari.
And more suspicious thing is i have 2 domains from them, both of them has CNAME to railway and one is still working, while another is not
2 years ago
happy to help
2 years ago
For now i think it's just a coincedence. One of this domains is just not resolving, while other is ok. I guess i'll write to namecheap's support
2 years ago
No news.
I'll try again in an hour and will keep you updated
2 years ago
Still no resolve for one address. I beleive we can close this topic, problem is not on railway side. Thanks anyway :)