An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
Hello @Le Van Khoa,
Thank you for using Q & A forum.
The Azure DNS Private Resolver must be accessible from the AKS subnet and properly linked to both VNets involved in the peering. You can verify this by checking the resolver’s configuration and ensuring it can resolve the names of resources in the peered VNet. Use commands like nslookup <hostname> to test DNS resolution from AKS nodes/pods.
Next, the network security groups (NSGs) associated with both the AKS VNet and the peered VNet. Make sure there are no NSG rules blocking traffic from AKS to the resources in the peered VNet. Sometimes, specific rules may inadvertently restrict access, leading to connectivity failures. You can review the NSG rules in the Azure portal to ensure that the necessary ports and protocols are allowed.
Lastly, remember that VNet peering allows for network-layer connectivity but does not automatically enable DNS name resolution. If the DNS settings are not configured correctly, AKS nodes/pods may struggle to resolve the private DNS names of resources in the peered VNet. Review the DNS configurations and ensure they are set up to facilitate name resolution across the peered VNets. Following these steps should help in diagnosing and resolving the connectivity issue.
If this answers your query, do click Accept Answer and Up-Vote for the same. And, if you have any further query do let us know.