Hello, I have just seen galaxy notifications on DNS modification https://galaxy-news.meteor.com/changelog/en/action-required-important-dns-update-for-your-hosted-applications--rDwu0D
This is a huge subject for us, as we are deploying white brands for our customers ( based on the same galaxy app ), so we have 94 domains to transfer.
I am starting ton think that this is not appropriate and that I might need a layer between galaxy and domains names ( like cloudfare ), but wanted to ask you guys how do you or would you handle such cases ?
Thanks
2 Likes
Hi @sabativi! Our DevOps team can help you find a solution. I’ll reach out to them.
If you could call them on our Galaxy chat or send me your username by DM, I can ask them to contact you.
Hello, my name is Thiago, and I’m a DevOps engineer here at Meteor. Unfortunately, you’ll need to repoint all 94 domains to the new DNS setup requested by Galaxy.
However, your idea of adding an intermediate layer, such as Cloudflare, can definitely simplify future changes. By pointing all your domains to this intermediary DNS and then directing the intermediary DNS to Galaxy’s new one, you can handle any future DNS updates centrally on Cloudflare, reducing the need to modify all domain records each time.
Let me know if you need any further assistance setting up this structure!
Hello @sabativi
We understand that migrating DNS for multiple domains is a critical task, especially with the volume of 94 domains for your white-label solution.
Galaxy offers several solutions within custom plans, integrated with platforms like Cloudflare and similar options, which can help manage and optimize this setup, making the required changes simpler.
Please start a conversation with us in the Galaxy chat so we can discuss these options in more detail and find the best solution for your needs. I’m available to help with anything you need. You can reach out to me directly.
Philippe Aquino
DevOps Lead / Galaxy Cloud
1 Like