Internal name resolution scenarios and options
Azure virtual network workloads need to be able to resolve internal and external domain names to IP addresses. A comprehensive Azure internal name resolution implementation should cover the translation of domain names for the following scenarios:
- Scenario 1 – name resolution for resources within the same virtual network
- Scenario 2 – name resolution for resources in different virtual networks
- Scenario 3 – name resolution for resources in connected on-premises networks (hybrid)
- Scenario 4 – name resolution for public domain names from VNet resources
Figure 2.8 shows an example of this. By making name resolution requests to its DNS resolver (server), VM1 (deployed into Azure VNET-1) should be able to resolve the private IP address for VM2 (deployed into a separate subnet in the same Azure VNet), it should be able to resolve the private IP address for VM3 (deployed into another Azure VNet...
