DNS migration to Azure DNS

Koteswara Pentakota 71 Reputation points

Our Name servers are currently pointing to BigRock where our DNS entires are hosted. For us to migrate this from BigRock to Azure DNS we are assuming that we export all DNS Entries from the Bigrock server to Azure DNS and redirect the Go Daddy Name servers from Bigrock to Azure.
Do we need to consider any more factors here.
We assume that the name server migration takes around 2-4 hours though in reality it can take up to 48 hours across the world. Is our assumption correct? We have our presence only in India as of now.

Azure DNS
Azure DNS
An Azure service that enables hosting Domain Name System (DNS) domains in Azure.
625 questions
Azure ISV (Independent Software Vendors) and Startups
Azure ISV (Independent Software Vendors) and Startups
Azure: A cloud computing platform and infrastructure for building, deploying and managing applications and services through a worldwide network of Microsoft-managed datacenters.ISV (Independent Software Vendors) and Startups: A Microsoft program that helps customers adopt Microsoft Cloud solutions and drive user adoption.
90 questions
{count} vote

3 answers

Sort by: Most helpful
  1. Takahito Iwasa 4,841 Reputation points MVP

    Hi, @Koteswara Pentakota

    I think your scenario is common.
    In addition, it's a good idea to make sure your Azure DNS limits and support coverage cover your scenario.
    For example, you need to contact Azure Support to increase the record set limit.


    1 person found this answer helpful.
    0 comments No comments

  2. GitaraniSharma-MSFT 48,531 Reputation points Microsoft Employee

    Hello @Koteswara Pentakota ,

    Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

    I understand that you would like to migrate your DNS name servers from BigRock to Azure. Currently your DNS delegation is between GoDaddy and BigRock but you would like to move it between GoDaddy and Azure DNS. Please correct me if my understanding is wrong.

    Azure DNS allows you to host a DNS zone and manage the DNS records for a domain in Azure. In order for DNS queries for a domain to reach Azure DNS, the domain has to be delegated to Azure DNS from the parent domain. Keep in mind Azure DNS isn't the domain registrar.
    Refer : https://learn.microsoft.com/en-us/azure/dns/dns-domain-delegation

    If my understanding is correct, then you need to follow the below steps:

    1) Obtain your existing DNS zone file from BigRock and then import that file into Azure DNS. Importing a zone file creates a new zone in Azure DNS if the zone doesn't already exist. If the zone exist, then the record sets in the zone file will be merged with the existing record sets.
    Refer : https://learn.microsoft.com/en-us/azure/dns/dns-import-export#introduction-to-dns-zone-migration

    2) Retrieve the name servers from your Azure DNS zone and update the parent domain in Go Daddy with the Azure DNS name servers.
    NOTE : When you copy each name server address, make sure you copy the trailing period at the end of the address. The trailing period indicates the end of a fully qualified domain name. Some registrars append the period if the NS name doesn't have it at the end. To be compliant with the DNS RFC, include the trailing period.

    Refer : https://learn.microsoft.com/en-us/azure/dns/dns-delegate-domain-azure-dns

    3) Wait for the DNS propagation and verify the delegation.

    Before you can successfully verify that the DNS delegation is working, you may need to wait at least 10 minutes after you complete the delegation. It can take a while for changes to propagate through the DNS system. So, yes you assumption is correct to wait for 24-48 hours.

    Kindly let us know if the above helped or you need further assistance on this issue.

    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

  3. Bas Pruijn 951 Reputation points

    In preparation I always feel the need to lower the TTL on the existing DNS. This more or less 'enforces' clients to request the DNS records more frequently, but also creates a faster switch-over to the new Azure DNS.

    I have always performed migrations this way. I do not have solid theoretical proof this approach helps though. Maybe someone else can elaborate.

    0 comments No comments