Dynatrace ActiveGate - Reaching ActiveGates through private DNS instead Azure's public DNS

nadeem_m — Mon, 05 Jun 2023 06:53:04 GMT

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.

https://learn.microsoft.com/en-us/azure/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances?tabs=redhat

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 the dnsEntryPoint parameter in the [connectivity] section using the following format:

dnsEntryPoint = https://<DOMAIN>:<PORT>

where <PORT> is optional and defaults to 443. For example for the ActiveGate:

[connectivity] dnsEntryPoint = https://FQDN:9999 (FQDN = private/local Fully Qualified Domain Name)

Please stop the ActiveGate before doing any changes in the custom.properties file and restart the ActiveGate post configuration.

Re: Dynatrace ActiveGate - Reaching ActiveGates through private DNS instead Azure's public DNS

ChadTurner — Thu, 08 Jun 2023 18:52:32 GMT

Thank you for Sharing this @nadeem_m

article Dynatrace ActiveGate - Reaching ActiveGates through private DNS instead Azure's public DNS in Troubleshooting

Dynatrace ActiveGate - Reaching ActiveGates through private DNS instead Azure's public DNS

Re: Dynatrace ActiveGate - Reaching ActiveGates through private DNS instead Azure's public DNS