Shulou(Shulou.com)06/03 Report--

Brief introduction

The domain name system, or DNS, is responsible for translating (or resolving) service names to their IP addresses. Azure DNS is a managed service for the DNS domain that uses the Azure infrastructure to provide name resolution. In addition to supporting Internet-oriented DNS domains, Azure DNS also supports dedicated DNS zones.

Azure private DNS provides reliable and secure DNS services to manage and resolve domain names in virtual networks without adding custom DNS solutions. With the dedicated DNS zone, you can use custom domain names instead of the names provided by Azure that are currently available. Using custom domain names can help you customize the virtual network architecture to best meet the needs of your organization. It provides name resolution for virtual machines (VM) within and between virtual networks. In addition, region names can be configured through split horizon view, allowing private and public DNS regions to share names.

To parse records for a private DNS zone from a virtual network, you must link the virtual network to that area. The linked virtual network has full access to resolve all DNS records published in a private area. In addition, automatic registration can be enabled on virtual network links. If auto-registration is enabled on the virtual network link, the DNS records of the virtual machines on that virtual network will be registered in the private zone. When auto-registration is enabled, Azure DNS also updates the zone record when a virtual machine is created, its IP address is changed, or the virtual machine is deleted. First, let's take a look at the official advantages of private DNS.

Azure dedicated DNS has the following advantages:

There is no need to use custom DNS solutions. Previously, many customers created custom DNS solutions to manage their virtual networks. The native Azure infrastructure can now be used to manage DNS zones, which relieves you of the burden of creating and managing custom DNS solutions.

Use all common DNS record types. Azure DNS supports A, AAAA, CNAME, MX, PTR, SOA, SRV, and TXT records.

Automates hostname record management. In addition to hosting custom DNS records, Azure automatically maintains hostname records for VM in the specified virtual network. In this scenario, you can optimize the domain name used without creating a custom DNS solution or modifying the application.

Hostname resolution between virtual networks. Unlike the hostname provided by Azure, private DNS zones can be shared between virtual networks. This feature simplifies cross-network and service discovery schemes, such as virtual network peer-to-peer interconnection.

Familiar tools and user experience. To make learning easier, this service uses mature Azure DNS tools (Azure Portal, Azure PowerShell, Azure CLI, Azure Explorer templates, and REST API).

Split horizon DNS support. With Azure DNS, you can create areas with the same name that resolve to different results within the virtual network and within the public Internet. A typical solution for split horizon DNS is to provide a dedicated service version for use within a virtual network.

Available in all Azure areas. The Azure DNS dedicated zone feature is available in all Azure areas in the Azure public cloud.

Function

Azure DNS provides the following features:

Automatically register a virtual machine from a virtual network that is linked to a private zone and has auto-registration enabled. The virtual machine registers (adds) to the private area as an A record pointing to its private IP address. When a virtual machine is deleted from a virtual network link with automatic registration enabled, Azure DNS also removes the corresponding DNS record from the linked private area.

Forward DNS resolution is supported between virtual networks linked to private areas. For DNS parsing across virtual networks, virtual networks are not explicitly required to interconnect with each other peer-to-peer. However, for other scenarios (such as HTTP traffic), you may want to interconnect virtual networks peer to peer.

Reverse DNS lookup is supported within the virtual network scope. A reverse DNS lookup of a private IP in a virtual network assigned to a private zone returns FQDN, including the host / record name and the zone name as a suffix.

You can see that there are still many supported features and scenarios, and Azure DNS is very convenient to use, so it's easy to take a look at it.

First, create a private DNS directly in portal.

After that, specify a domain name that we need to use, because it is used in the private network, so it doesn't matter to specify some other people's domain names.

After the creation is completed, we start to link to VNET. There are two VNET in our environment, one on a different region, and we use global peering to get through.

Just select the VNET you want.

Similarly, add another VNET

Then we see that two machines in the two VNET are automatically added to the Azure DNS.

Both nodes can access each other through the hostname+ domain name.

、

In addition, we can also add MX records, SRV these records

After the addition is completed, the corresponding MX record is resolved on the vm.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.