Resolving conflicts in Azure DNS

An conflict may occur in Azure DNS if two people or two processes try to modify a DNS record at the same time. How can you it determine which one wins? And does the winner know that they’ve just overwritten changes created by someone else?

Azure DNS uses Etags to handle concurrent changes to the same resource safely. Each DNS resource (zone or record set) has an Etag associated with it. Whenever a resource is retrieved, its Etag is also retrieved. When updating a resource, you(or the creator of DNS record) have the option to pass back the Etag so Azure DNS can verify that the Etag on the server matches. Since each update Read More »

Create Azure DNS zone and records

The most of internet relies on TCP/IP protocol. In order to reach a service/machine, you need to know its ip address. In its essence, DNS or Domain Name System is a network service which is responsible for resolving a website/service name to its IP address. Azure DNS is a hosting service for DNS domains, providing name resolution using Microsoft Azure infrastructure. It uses Anycast networking, so DNS resolution occurs from closet available DNS server.

In order to start hosting your domain, Read More »

An overview on Azure DNS

Microsoft has announced general availability for Azure DNS service in all public regions on Monday September 26, 2016. With this announcement, Azure DNS can now be used for production workloads. It is supported via Azure Support, and is backed by a 99.99% availability SLA.

As with other Azure services, Azure DNS offers usage-based billing with no up-front or termination fees. Azure DNS pricing is based on the number of hosted DNS zones and the number of DNS queries received (in millions).Read More »