Custom Domain not working after move to Kubernetes (solved by time)

0
Hi all,   Just did a deployment on Production which included a move to Kubernetes, and for the first 20 minutes the app was unreachable by custom domain. Anyone else experience this (and/or have tips how to prevent this for future apps)?   I've submitted a support ticket but no response there yet.
asked
1 answers
0

Response from Mx support:

"When your application is moved from Cloud Foundry to Kubernetes, the application will be listening on a new endpoint, while the URL remains the same. Your DNS provider will have cached the DNS record for your application, where it still points to the old Cloud Foundry endpoint. Because your app is no longer running there, your browser will show the Offline page. Your application will be visible again in your browser once your DNS cache is cleared. After that, you will get the updated DNS record for your application, which points to the new Kubernetes endpoint. Alternatively, you can try opening your application in a different browser."

answered