In my Azure environment I have private SQL Server. To access SQL Server and databases I use a private endpoint. When I connect to SQL from VM in the same Virtual Network I have no problem. I have AKS in the same Virtual Network I try to connect to the database from pod but Kubernetes DNS didn’t resolve SQL Server FQDN correctly. DNS name resolved to external IP but private SQL didn’t have external access.

This is example how SQL Server resolved from VM:

nslookup *****************.database.windows.net
Server:     127.0.0.53
Address:    127.0.0.53#53

Non-authoritative answer:
*****************.database.windows.net  canonical name = *****************.privatelink.database.windows.net.
Name:   *****************.privatelink.database.windows.net
Address: 172.0.8.4

This is correct address to Private Endpoint

And how it resolve from pod in AKS cluster:

kubectl exec -it dnsutils -- nslookup *****************.database.windows.net

Server:     10.0.0.10
Address:    10.0.0.10#53

Non-authoritative answer:
*****************.database.windows.net  canonical name = *****************.privatelink.database.windows.net.
*****************.privatelink.database.windows.net  canonical name = dataslice6.******.database.windows.net.
dataslice6.******.database.windows.net  canonical name = dataslice6*******.trafficmanager.net.
dataslice6*******.trafficmanager.net    canonical name = cr5.******-a.control.database.windows.net.
Name:   cr5.*******-a.control.database.windows.net
Address: 40.78.225.32

How I can set connection pods from AKS to SQL Private Endpoint?