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

**URL:** <https://community.dynatrace.com/t/dynatrace-activegate-reaching-activegates-through-private-dns-instead-azures-public-dns/40044>\
**Category:** Troubleshooting\
**Tags:** activegate, azure, oneagent\
**Created:** [June 2, 2023, 12:19pm UTC](https://community.dynatrace.com/t/dynatrace-activegate-reaching-activegates-through-private-dns-instead-azures-public-dns/40044 "2023-06-02T12:19:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nadeem\_m](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/nadeem_m/32/18048_2.png) [@nadeem\_m](https://community.dynatrace.com/u/nadeem_m)\
**Post date:** [June 2, 2023, 12:19pm UTC](https://community.dynatrace.com/t/dynatrace-activegate-reaching-activegates-through-private-dns-instead-azures-public-dns/40044/1 "2023-06-02T12:19:54Z")

</div>

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.

> **[Azure Virtual Network Name Resolution Guide](https://learn.microsoft.com/en-us/azure/virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances?tabs=redhat)**
>
> Learn how to configure DNS name resolution for Azure virtual networks. Explore Azure-provided DNS, private DNS zones, and custom DNS servers for virtual machines and hybrid solutions.

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

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

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

```markup
[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.

---

<div class="post-metadata">

**Author:** ![ChadTurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/chadturner/32/161_2.png) [@ChadTurner](https://community.dynatrace.com/u/ChadTurner)\
**Post date:** [June 8, 2023, 6:52pm UTC](https://community.dynatrace.com/t/dynatrace-activegate-reaching-activegates-through-private-dns-instead-azures-public-dns/40044/2 "2023-06-08T18:52:32Z")

</div>

Thank you for Sharing this&nbsp;[@nadeem\_m](https://community.dynatrace.com/user/47494)
