Why does a VM still resolve a storage account publicly after a private endpoint was added?
A storage private endpoint and its DNS record exist. A VM in a connected network still resolves the ordinary blob hostname to a public address. The VM uses a custom DNS server, while another VM using the intended Azure resolver gets a private address. The application configuration has not changed. Which part of the DNS chain should be investigated?