a year ago
Is it normal for the supplied URL to put in the DNS record to say there is nothing here if entered directly into my browser?
The website is deployed and available at the public networking railway URL in the list in the Networking settings, but the URL provided to put in the DNS record says nothing is there when I navigate directly to it.
Is there some magic happening after it verifies the DNS record or is something wrong? I'm nervous that the DNS record I applied is going to take affect and take down the existing website at the prior location.
0 Replies
It seems like it works just fine on the machine where the DNS record is updated, so that's cool! I don't have an actual issue then but I'm curious what networking sorcery is happening here
a year ago
railways proxy takes about a minute to register new routes, are you still seeing this behaviour?
Technically yes - the custom domain actually works (Site is live) - the thing that confused me was just that the URL it supplied me to put in DNS still seems to not actually work if entered directly into the browser. It's been years since I did this stuff so maybe I'm missing something, but I figured I would sanity check the URL before punching it into the DNS and was surprised that it just says "Nothing here yet". I'm even more surprised that putting that URL in the DNS worked
a year ago
ohhh i see what you mean now, you're talking about the random cname it gave you. that is just a random cname and only serves to resolve the ip
a year ago
so you could have entered burger.up.railway.app into your dns settings when setting up the custom domain and it would have worked all the same
Oh I see, railway is resolving the IP based on the domain that the request is coming for
a year ago
not quite, they use host based routing, the cname they gave you is just in place so your dns resolver can resolve the correct ip