title: Azure Virtual Machine cannot resolve DNS entry of Application Gateway
body: <p>I have the following situation:</p>
  <p>If I deploy an application (Deployment, Service and Ingress) in my kubernetes cluster, my ingress deployment is being automatically added to my application gateway (I am using the Azure Application Gateway Ingress Controller; <a href="https://azure.github.io/application-gateway-kubernetes-ingress/annotations/" rel="nofollow noreferrer">https://azure.github.io/application-gateway-kubernetes-ingress/annotations/</a> ). So far so good.
  That means that my application can be reached via my application gateway via https://my-app-gateway-public-ip/myAppPath/. Also, I have an additional private DNS zone which makes my app accessible via https://dns-name/myAppPath.</p>
  <p>Additionally, we have an AADDS in combination with a Bastion Service. Deployed some virtual machines and the virtual machines use the DNS resolver of the AADDS (for authentication against the AAD).</p>
  <p>The problem is: If I am outside of the cloud, I can nslookup the dns or can access the site via the ip, but I cannot do that with my virtual machines. My DNS server (within the AADDS) is unable to resolve the dns or accessing the ip. I am wondering what the issue is.</p>
  <p>The bastion and AADDS are in different subscriptions and therefore different virtual networks. I established already a peering between those virtual networks (or the authentication between the AADDS and the VMs wouldn't work).</p>
  <p>The kubernetes cluster and the application gateway are also in a different subscription, but no peering has been done so far.</p>
  <p>Are there any hints what I could be missing?</p>
  <p>Kind regards</p>