Sighhh,,, this is my fault, i just saw a typo i made with the storage account name using "mystro..." instead of "mystor...", and unluckily for me someone else had actually created the "mystro..." version as well !!
Private endpoint not working
I have been having trouble with private endpoints returning the public IP instead of the private IP. To troubleshoot I decided to follow a published Microsoft article literally step for step, but nslookup still resolves to the public address. Article -> https://learn.microsoft.com/en-us/azure/private-link/tutorial-private-endpoint-storage-portal.
Below is the output from nslookup from a VM in the vNet this article created. Any suggestions please as this is also affecting other endpoints i try to setup, none of them work correctly and I cannot work out why?
- Private DNS zone created successfully and linked to vNet with status "Completed"
- Private DNS zone has DNS A record of storage account name and private IP
- Private link created successfully
- Private endpoint has connection status "approved"
C:\>nslookup mystroageaccount.blob.core.windows.net
Server: UnKnown
Address: 168.63.129.16
Non-authoritative answer:
Name: blob.dm2prdstr03a.store.core.windows.net
Address: 20.150.95.4
Aliases: mystroageaccount.blob.core.windows.net
2 answers
Sort by: Most helpful
-
-
Mark Fuller 42 Reputation points
2022-03-17T23:36:40.05+00:00 This was my fault with a simple typo, so is no longer an issue.