Test name resolution first
From the affected VM, run nslookup or Resolve-DnsName against the target service name. Confirm the name resolves to the expected private address.
Check private DNS zones
Verify the required private DNS zone exists and contains the expected record or is configured for automatic registration where supported.
Check virtual network links
Confirm the client VNet is linked to the private DNS zone.
Check custom DNS
If the VNet uses custom DNS servers, verify they can resolve the private zone or forward the required queries correctly.
Check route and NSG behavior
After DNS is correct, validate routing and security rules to the private endpoint address.
Validate from the application host
Repeat the test from the exact VM or application subnet that experiences the issue.
Explore more TechRunbook guides
Browse practical troubleshooting guides, PowerShell scripts, checklists and infrastructure resources for your environment.
Browse all articles →