Azure DNS Public

Handian Sudianto 4,166 Reputation points
2024-03-20T11:24:20.1366667+00:00

Hello,

Currently my DNS handle by vendor/ISP, and i have plan to move to Azure.

Anyone know here what best practice how to migrate my DNS with the records from 3rd party to the azure with minimal downtime, especially downtime for propagate?

Azure DNS
Azure DNS
An Azure service that enables hosting Domain Name System (DNS) domains in Azure.
603 questions
{count} votes

Accepted answer
  1. GitaraniSharma-MSFT 48,011 Reputation points Microsoft Employee
    2024-03-20T11:41:53.7133333+00:00

    Hello @Handian Sudianto ,

    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 with records from 3rd party to Azure.

    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 the 3rd party 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 exists, 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

    1. Retrieve the name servers from your Azure DNS zone and update the parent domain in the 3rd party DNS registrar 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

    1. 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. DNS propagation takes time and there is no way to reduce this downtime. You may have to wait for 24-48 hours.

    Refer: https://learn.microsoft.com/en-us/azure/dns/dns-faq#how-long-does-it-take-for-dns-changes-to-take-effect-

    DNS propagation can't be instantly expedited in the traditional sense because it depends on the caching policies of ISPs and DNS servers worldwide, which are beyond the control of any single entity.

    However, you can try to minimize the impact of propagation delays by lowering the TTL (Time To Live) of your DNS records. Before making DNS changes, reduce the Time to Live (TTL) values for the DNS records. A lower TTL tells DNS servers to refresh their cache more frequently. Do this several days in advance so that when you do make the change, DNS servers worldwide will update the records more quickly.

    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.

    0 comments No comments

0 additional answers

Sort by: Most helpful