Mendix on Azure resolving private IP address

0
Hi,We have setup a couple of Mendix on Azure applications. These are setup as completely private with no public access. Grafana is resolving to the public IP and having a hard time figuring out how to fix this. We are using a central Private DNS zone but cannot link the managed application to it as you can't edit the virtual network links. I have setup according to this documentation Enabling Connectivity between Mendix on Azure and Other Private Networks | Mendix Documentation a private DNS zone for azure.mendixapps.io and the actual application is resolving fine to the private IP but can't get grafana to resolve to the private IP. Also setup the Private Link Service and Private endpoint according to the documentation but did not help. Any help would be appreciated if someone has seen the same issues.
asked
1 answers
0

Hi Björn,

It sounds like the Mendix application side is already resolving correctly to the private IP, so I would focus on DNS resolution from the Grafana environment.


A few things I would check:

  • From the Grafana host/container, run nslookup <your-app>.azure.mendixapps.io or dig <your-app>.azure.mendixapps.io and verify which DNS server is being used.
  • Make sure the azure.mendixapps.io Private DNS zone is accessible from the VNet/subnet where Grafana is running.
  • If you are using a central Private DNS zone, verify that the DNS queries from the Grafana VNet are actually forwarded to the DNS infrastructure hosting that zone.
  • Check whether Grafana is using Azure-provided DNS (168.63.129.16), a custom DNS server, or another DNS resolver. The resolution path can be different depending on this configuration.
  • Also verify that there isn't another public DNS record taking precedence over the private record.


Since the Mendix application itself resolves to the private IP but Grafana resolves to the public IP, comparing the output of nslookup/dig from both environments would be very useful.


The Private Link configuration is also worth checking, but I would first establish exactly which DNS resolver Grafana is querying and whether that resolver has visibility of the azure.mendixapps.io Private DNS zone.


If you can share the nslookup/dig output from the Grafana environment (with any sensitive information removed), it should be easier to narrow this down.


Kindly mark this as the accepted answer if it helps.

answered