Traffic is routed to and from this virtual IP address through the subnet gateway. Fun fact, some geolocation services will report this IP as being based out of Hong Kong and I’m sure you can imagine how that works when something like a WAF is in place with regional IP restrictions. The address is static and is the same for any VNet you create in every Azure region. It provides functionality such as virtual machine (VM) agent communication of the VM’s ready state, health state, enables the VM to obtain an IP address via DHCP, and you guessed it, enables the VM to leverage Azure DNS services.
This public IP address is owned by Microsoft and is presented as a virtual IP address serving as a communication channel to the host node for a number of platform resources. If you’ve ever done anything even basic in Azure, you’ve probably run into this address or used it without knowing it. If any of those are unfamiliar to you, take some time to review the basics then come back to this post.īefore we jump into the DNS options in Azure, I first want to cover the 168.63.129.16 address. I’m going to go into this assuming you have a basic knowledge of DNS and understand the namespaces, various record types, forward and reverse lookup zones, recursive and iterative queries, DNS forwarding and conditional forwarding, and other core DNS concepts. Specifically, we’re going to look at the options for private DNS in Microsoft Azure and what the positives and negatives are of each pattern. Yes folks, we’re going to cover Domain Naming System (DNS).
#Annael2 cloudapp net series
In this series of posts I’m going to talk about a technology, that while old, still provides a critical foundational service.
0 kommentar(er)
