internal DNS zone for Container Apps is not being injected into my VNet

Hi there, Azure Container Apps Environments deployed with internal ingress are not injecting the required internal DNS zone into the VNet. As a result, no internal FQDNs resolve from any VM inside the same VNet, even though the environment and container apps deploy successfully and show internal ingress endpoints in the portal.

This issue persists across multiple new environments, multiple new subnets with no custom networking.

Would greatly appreciate help here.

Some additional details:

1. Container Apps Environment created with:
   • Public access disabled
   • VNet integration enabled
   • Internal load balancer assigned (private VIP)
2. Container App created with:
   • Ingress enabled
   • Traffic limited to Container Apps Environment
   • Internal FQDN generated, e.g.: https://mancont312.internal.bravewater-d9e2aebd.eastus2.azurecontainerapps.io/
3. From a VM in the same VNet using Azure DNS (168.63.129.16), DNS resolution fails: nslookup internal.eastus2.azurecontainerapps.io → NXDOMAIN The root zone (internal.eastus2.azurecontainerapps.io) does not exist, which indicates the internal DNS zone was never injected into the VNet.