Azure Public DNS ZONE create records Transfer from Godaddy to Azure DNS

Learn how to configure your Azure Public DNS Zones and Create Azure Public DNS Records.

You can Manage your Public DNS from Azure.

You can configure Azure DNS to resolve host names in your public domain. For example, if you purchased the contoso.xyz domain name from a domain name registrar, you can configure Azure DNS to host the contoso.xyz domain and resolve www.contoso.xyz to the IP address of your web server or web app.

Azure DNS SERVICE is a hosting service for DNS domains that provides name resolution by using Microsoft Azure infrastructure. By hosting your domains in Azure, you can manage your DNS records by using the same credentials, APIs, tools, and billing as your other Azure services.

Azure DNS SERVICE can manage DNS records for your Azure services and provide DNS for your external resources as well. Azure DNS is integrated in the Azure portal and uses the same credentials, support contract, and billing as your other Azure services.

Azure SERVICE DNS billing is based on the number of DNS zones hosted in Azure and on the number of DNS queries received

Microsoft Azure provides the ability to create a DNS public zone and manage it from the Azure Portal. If you are already an owner of a public DNS zone, you can change the name server (NS records) to point to those of Azure.

If you have many public DNS zone, it can be a pain to manage. First the interface can be different depending on the providers. Secondly, lot of the time the interface is not user friendly and you can’t automate the DNS record creation.

If you manage your DNS zone from Microsoft Azure, you have a unified interface and you can automate the DNS record creation through ARM, AzureCLI or PowerShell. This service is not expensive compared to the advantage brought by Azure DNS (the below capture comes from https://azure.microsoft.com/en-us/pricing/details/dns/)

Azure-provided name resolution
Azure provided name resolution provides only basic authoritative DNS capabilities. If you use this option the DNS zone names and records will be automatically managed by Azure and you will not be able to control the DNS zone names or the life cycle of DNS records. If you need a fully featured DNS solution for your virtual networks you must use Azure DNS private zones or Customer-managed DNS servers.

Along with resolution of public DNS names, Azure provides internal name resolution for VMs and role instances that reside within the same virtual network or cloud service. VMs and instances in a cloud service share the same DNS suffix, so the host name alone is sufficient. But in virtual networks deployed using the classic deployment model, different cloud services have different DNS suffixes. In this situation, you need the FQDN to resolve names between different cloud services. In virtual networks deployed using the Azure Resource Manager deployment model, the DNS suffix is consistent across the all virtual machines within a virtual network, so the FQDN is not needed. DNS names can be assigned to both VMs and network interfaces. Although Azure-provided name resolution does not require any configuration, it is not the appropriate choice for all deployment scenarios, as detailed in the previous table.
#PaddyMaddy #cloudComputing #azuretutorial #microsoftazuretutorialforbeginners #azureforbeginners #azurebasics #microsoftazuretraining #Az900 #AZ500, #microsoftazurecertification, #AZ303 #az300 #az104 #paddyMaddy #azuretraining