azure private dns zone and vnet

 

Given that we have a private dns zone and vnet routing capabilities, if i were to lookup a server name say db.private.contoso.com, how does it gets resolve. 

By default, it goes through Azure default routing and if that fails, it will try to use a DNS zone and in my case a private dns zone. 

Azure routing 


MyVM01 is auto-registered after DNS Zone is associated to a VNET. In this case, it uses cloudapp


Private DNS

When i lookup my db.private.contoso.com, it tries to use cloudapp then falling back to my private DNS zone as you can see here. 



So key takeaways, when you create DNS zone, remember to link it to your vnet.  It uses azure default routing before falling back on DNS zone. 

To learn how to create a private dns zone, you can follow the guide here.

https://learn.microsoft.com/en-us/azure/dns/private-dns-getstarted-portal



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