on 02 Jun 202301:19 PM - edited on 05 Jun 202307:53 AM by MaciejNeumann
Configuration change for reaching ActiveGates through private DNS instead Azure's public DNS.
If you have created VMs in Microsoft Cloud Services such as azure and have got a public DNS name which is not resolvable from other private/virtual networks and have provided a private DNS name to the virtual machines. It might be difficult to reach the ActiveGates, if Oneagents are installed in other local virtual networks.
If you want Oneagents to try the private DNS names instead of azure's public (which might not be reachable from other virtual networks), you would require to do a change in the custom.properties file. This works exactly like the configuration of the load balancer for ActiveGates.
Configure thednsEntryPointparameter in the[connectivity]section using the following format:
dnsEntryPoint = https://<DOMAIN>:<PORT>
where<PORT>is optional and defaults to443. For example for the ActiveGate: