How to reset the DNS zone in Azure DNS so that it propagates correctly in the world

Charles-Henri Blanchard 40 Points de réputation
2026-06-16T17:39:09.2233333+00:00

Hello,

My DNS zone isn't propagating correctly when I query DNS propagation sites.

How is it possible to reset the DNS zone without deleting it so that it propagates again?

Thanking you in advance,

Charles-Henri Blanchard

Azure DNS
Azure DNS

Service Azure qui active l’hébergement de domaines DNS (Domain Name System) dans Azure.

0 commentaires
Réponse acceptée par l’auteur(e) de la question
Venkatesan S 10,830 Points de réputation Personnel externe de Microsoft Corporation Modérateur
2026-06-16T18:13:05.1633333+00:00

Hi Charles-Henri Blanchard,

Thank you for reaching out about your DNS zone propagation issue.

Unfortunately, there is no mechanism to "reset" a DNS zone and force DNS propagation to occur again without deleting the zone. DNS propagation is governed by DNS caching and TTL (Time-To-Live) values across recursive DNS resolvers on the internet, which means you cannot manually restart the propagation process.

If your DNS zone is hosted in Azure DNS, here are the key steps to verify and troubleshoot:

  1. Confirm domain delegation – Ensure your domain registrar is pointing to the exact Azure DNS name servers assigned to your zone (e.g., ns1-XX.azure-dns.com, ns2-XX.azure-dns.net, etc.). You can find these in the Azure Portal under your DNS zone.
  2. Verify DNS records – Check that the DNS records in your Azure DNS zone contain the expected values (A, CNAME, MX, TXT, etc.).
  3. Query authoritative name servers directly – Use commands like dig or nslookup to query Azure's authoritative name servers directly: 
       dig yourdomain.com @ns1-XX.azure-dns.com
    If the records are correct here, your zone is functioning properly, and any remaining delay is due to caching outside of Azure DNS.
  4. Review TTL values – Check the TTL configured on your affected records. While Azure DNS updates are typically reflected on authoritative name servers within minutes, recursive resolvers may continue serving cached responses until the TTL expires.

If the authoritative Azure DNS name servers return the correct records, this generally indicates the DNS zone is working as expected, and any remaining delay is due to standard DNS caching on the internet.

Official Documentation

For more details, please refer to these Microsoft resources:

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

Please do not forget to 210246-screenshot-2021-12-10-121802.pngand “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Cette réponse vous a-t-elle été utile?

1 personne a trouvé cette réponse utile.

1 réponse supplémentaire

Trier par : Plus récent
Le plus utile Plus récent Plus ancien
  1. Charles-Henri Blanchard 40 Points de réputation
    2026-06-16T18:39:18.36+00:00

    Hello,

    Thank you for the clarifications.

    After retesting, at a different site (https://digwebinterface.com/), the propagation of the DNS zone seems to be good.

    The problem must have come from the caching of the internet.

    My NSs are registered at the level of my registrar, they are those of Azure DNS.

    Thanks again,

    Charles-Henri Blanchard

    Cette réponse vous a-t-elle été utile?

    0 commentaires

Votre réponse

Les réponses peuvent être marquées comme « Acceptées » par l’auteur(e) de la question et « Recommandées » par les modérateurs, ce qui aide les utilisateurs à savoir que la réponse a résolu le problème de l’auteur(e).