Multiple DNS with Meshcentral

[Skyline643]

Hi all,

Our MeshCentral server and agents are growing very fast. At the moment of starting, Mesh has been created to refer to a freeddns instead of a public IP. So when installing an agent, the agent connects to that chosen freeddns name and specific port.
Because of becoming more professional we want to add another DNS-name or 2nd DNS-name (and maybe forwarding)?

What is the best practice?

If we just change the DNS, the 'old' and still active agents won't connect anymore I think?
Maybe it's time to setup an NGINX of Apache relay server to do this? And maybe put some more security like geoblocking at the same time? Or can we just simply forward the traffic from the company DNS to the freeddns and will the meshagents still find the right way to the server without any issues?

Update: I found the option to add DNSrelay in the config.json but I'm not sure of this works in Version 1.1.48 as well?

[Skyline643]

Ok, I tested a few things:

• DNS relay doesn't work in v1.1.48
• Adding extra code in the config.json like:
  { "settings": { "cert": "primary.example.com", "port": 443 }, "domains": { "": { "title": "HoofdDomain", "dns": "primary.example.com" }, "Extra": { "title": "ExtraDomain", "dns": "extra.example.com" } } }

This gives a corrupt config.json
Are there other things I can try? There's also a SSL cert update (default one in Mesh) we use. Of course I want the 2nd DNS name to be secure as well.

Or is it better to move everything to the other DNS name? Proble is that I don't want to update 400+ agents manually...