2 years ago
Project ID: 1403d8a3-d1fc-487a-9eac-065da725466c
I am switching my main production domain from Heroku to Railway and in doing so adding the domain to Railway.
Once I did Railway gave me a value to update. I made the change. Every CName checker I can find already has the updated information which shows Railway as the target however Railway still sees the old value and won't issue the certificate reporting that the value is incorrect.
I think something might be cached on Railways DNS side.
I created a second CName for the same domain 25 mins later and that one update perfectly in Railway almost immediately so it seems to be an issue when changing a pre-existing CName's value that is causing it to be stuck or slow.
The CNAME is rexy.futurefictionacademy.com
5 Replies
2 years ago
railway uses 8.8.8.8 for the DNS lookup.
remove the domain from railway and add it back
I deleted the domain rexy.futurefictionacademy.com and re-added it. It changed the CNAME value.
But it still shows as incorrect and still shows an old CNAME on the DNS
Incorrect value "deep-elderberry-dgv4chwdwcbcv4a7ifcplqei.herokudns.com"
But the current CNAME showing for rexy.futurefictionacademy.com is
Here is what it looks like when I run a Cname Lookup on rexy.futurefictionacademy.com (in pic)
It seems like the deleting and putting it back in didn't change the cached value it is pulling.
2 years ago
no problem!