Public Networking DNS Refresh
ethanharwood97
HOBBYOP

2 months ago

I need help refreshing the DNS on my public network. I should be launching this app this weekend and all other apps have refreshed instantly. However railway is taking longer then 24hrs. Can someone help lease

$10 Bounty

4 Replies

Railway
BOT

2 months ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!


dalinkstone
FREE

2 months ago

You could try a DNS cache flush as was mentioned prior, or you could switch to Cloudflare's 1.1.1.1 by visiting their page that has walkthroughs for almost every device: https://developers.cloudflare.com/1.1.1.1/setup/


dalinkstone

You could try a DNS cache flush as was mentioned prior, or you could switch to Cloudflare's 1.1.1.1 by visiting their page that has walkthroughs for almost every device: https://developers.cloudflare.com/1.1.1.1/setup/

ethanharwood97
HOBBYOP

2 months ago

Sorry its not my ISP. Its Railways Public Networking

Access your application over HTTP with the following domains.

I have set up a custom domain and changed the CName. However its saying "Port 8080

·

Metal Edge

·Waiting for DNS update·Show instructions"


dalinkstone
FREE

2 months ago

The list of gotcha's for custom domain names can be found here: https://docs.railway.com/guides/public-networking#custom-domains:~:text=dynamic%20ALIAS%20records.-,Additional%20context,-Generally%2C%20direct%20CNAME. Depending on the provider you are using you may need to use a different record type. Similarly, if you are using any of the CName supported providers, you can only ever have a single record using the same host. For example, an A (Alias) record that uses the @ host to point to an old server and the new Railway CName record that uses the @ host will create a conflict.

For me, I use namecheap and I had an A record using the @ host pointing to an old server. When I created the CName record I had to delete that old record so that DNS updates would populate appropriately.


Loading...