testing reachability of private endpoint for a vnet

 

private endpoint lab to test out storage account reachability from a vnet. 

1. setup vnet 

2. setup storage account and enable a private link and place in default.

3. setup linux vm in default subnet - test if the private link is resolvable

3. setup linux vm in another subnet  test if the private link is resolvable. 


Doing a nslookup on a non-vnet machine. 



nslookup from vm1 on the same vnet and subnet. You can see it resolve to an internal ip.


nslookup from vm2 on the same vnet and different subnet (subnet2). You can see it resolve to an internal ip.


Wire server with address 168.63.129.16 is scope to a VNET. This means, you just need to use this to resolve a private endpoint for a VNET. 

- Hostname - probably not a good idea as it might trip you at some point.

- Conditional forwarders - scope to a VNET 

- Forward Lookup zone - if you're trying to resolve with a different VNET. Say you might have multiple VNET and you need your application to be able to resolve to an internal ip instead of public ip. With this approach we need to add a new record when a new private link has been created or removed. 




Comments

Post a Comment

Popular posts from this blog

The specified initialization vector (IV) does not match the block size for this algorithm

Image
If you're getting  exception when trying to assigned key to a symmetric key and getting error message below :- The specified initialization vector (IV) does not match the block size for this algorithm And your code probably look like something below :- Then you need to go into debug mode and start looking into the supported size for IV as shown in diagram below :- As you can see, IV is 16 bytes, so you need to provide 16 bytes. The same goes for Key field too, if you're adding anything to it. As long as you provide a valid key size, then we're good and you're code will be ready.
Read more