Azure managed domain, and dns not propagating

Question

Azure managed domain, and dns not propagating

juan bodniza 20

No matter what I try (frontdoor etc) the dns for my domain is not propagating.

It looks ok on the dns setup on azure (www and a subdomain), but it never propagates globally.

Site is down no for 4 weeks.

And azure provides no support unless I pay $1,000 per month?

What kind of service is this?

My domain was registered with azure. Worked ok for 2 years, then I deleted old dns zone re-add it and now it never propagates (even if wait entire week).

Sai Prasanna Sinde 5,240 Reputation points Microsoft External Staff

2025-03-19T08:39:00.9633333+00:00
Hi @juan bodniza

We apologize for the inconvenience caused.

First, you need to obtain the current set of name servers that Azure has assigned to the recreated DNS zone.

Log into the Azure portal at portal.azure.com, navigate to the Resource group where the DNS zone was recreated, and select the DNS zone itself.

On the overview page of the DNS zone, you will see a list labeled name servers displaying four distinct entries, such as ns1-xx.azure-dns.com, ns2-xx.azure-dns.net, ns3-xx.azure-dns.org, and ns4-xx.azure-dns.info.

It is crucial to accurately copy all four of these name server names.

Since the domain is registered with Azure, I assume that the registrar is likely Azure App Service Domains (correct me if I'm wrong) if the purchase was made directly through Azure.

In this case, search for App Service Domains within the Azure portal, select the specific domain name, and look for either DNS settings or an Advanced domain management portal, which might redirect to a GoDaddy interface, as Azure uses GoDaddy for App Service Domain registration.

If the domain was registered through a third-party registrar (like GoDaddy or Namecheap) but is hosted in Azure DNS, log in to the account directly with that registrar and locate the DNS management section for the domain.

Identifying the exact registrar is essential, as this is where the critical NS records need to be updated. For more info, please refer the document.

Once you have access to the DNS management interface of the domain registrar, locate the section for managing Name Servers (NS records).

Here, you will need to remove the existing name server entries and replace them with the four Azure DNS name servers.

Ensure that all four name servers provided by Azure are used to maintain redundancy and reliability.

Some registrars may require a trailing period (.) at the end of each name server address, so consult your registrar's documentation if you are not sure.

Updating the NS records at the registrar is crucial for resolving the DNS propagation issue, as it links the domain name to the new authoritative DNS servers hosted in Azure. Please refer this similar thread for guidance.

After updating the NS records at the registrar, it is important to verify that these changes have been recognized by the global DNS system. You can utilize online DNS propagation checker tools such as https://dnschecker.org/ or https://www.nslookup.io/dns-checker/to check if the new Azure name servers are being reported for their domain across various locations worldwide.

On these tools, you should enter their domain name and select "NS" as the record type to perform the check. Additionally, command-line tools like nslookup (available on Windows) or dig (available on macOS and Linux) can be used to directly query the Start of Authority (SOA) record of the domain, specifically targeting one of the new Azure DNS name servers.

Kindly let us know if the above helps or you need further assistance on this issue.
juan bodniza 20 Reputation points

2025-03-19T21:33:25.33+00:00

Thanks for your answer/suggestion. But I already tried this.

The app service domain sends me to screens within azure (not outside registrar) to edit the DNS records and everything looks fine there.

However these changes are never propagated to any DNS outside out of this screen. (even after waiting weeks).

Already tried this several times. Its like this page is not connected to the actual DNS propagation. (but everything looks ok on this screen -- the dns records are there).

I checked with online tools and the domain says registered with wildwestdomains.

I tried to login in that website to manage dns but when login takes me back to the same azure dns management screens lol.

So at this point i dont know what else to do.

Ugly bug in azure and my site/dns down.

Help please!
Sai Prasanna Sinde 5,240 Reputation points Microsoft External Staff

2025-03-20T10:14:26.1133333+00:00

Hi @juan bodniza

I have initiated a private message. Please check and provide the requested details.

Also, could you please verify and confirm if your domain has expired?

Check, Renew the domain.

Additionally, please refer to this thread and check if it works for you.
juan bodniza 20 Reputation points

2025-03-25T19:31:30.22+00:00

The issue is azure dns shows 04 (instead of 02) and even deleting it and readding it gets assigned to 04.

And if i try to login in wildwestdomains to change it, redirects me to azure.

I registered the domain on azure
Sai Prasanna Sinde 5,240 Reputation points Microsoft External Staff

2025-03-27T16:27:33.8466667+00:00

Hi @juan bodniza

As documented here, Azure DNS is not a domain registrar. Azure DNS allows you to host a DNS domain and manage the DNS zone records.

To host your domain in Azure, the zone must be created in Azure and delegated to Azure's authoritative DNS servers with a domain registrar.

You need to update the latest Azure name servers with your domain registrar to ensure proper DNS propagation and name resolution.

Since the issue occurs when logging into your domain registrar's account, please reach out to their support team for assistance in resolving it.

Accepted answer

0 additional answers

Your answer

juan bodniza 20 Reputation points

2025-03-19T21:33:25.33+00:00

Thanks for your answer/suggestion. But I already tried this.

The app service domain sends me to screens within azure (not outside registrar) to edit the DNS records and everything looks fine there.

However these changes are never propagated to any DNS outside out of this screen. (even after waiting weeks).

Already tried this several times. Its like this page is not connected to the actual DNS propagation. (but everything looks ok on this screen -- the dns records are there).

I checked with online tools and the domain says registered with wildwestdomains.

I tried to login in that website to manage dns but when login takes me back to the same azure dns management screens lol.

So at this point i dont know what else to do.

Ugly bug in azure and my site/dns down.

Help please!
Sai Prasanna Sinde 5,240 Reputation points Microsoft External Staff

2025-03-20T10:14:26.1133333+00:00

Hi @juan bodniza

I have initiated a private message. Please check and provide the requested details.

Also, could you please verify and confirm if your domain has expired?

Check, Renew the domain.

Additionally, please refer to this thread and check if it works for you.
juan bodniza 20 Reputation points

2025-03-25T19:31:30.22+00:00

The issue is azure dns shows 04 (instead of 02) and even deleting it and readding it gets assigned to 04.

And if i try to login in wildwestdomains to change it, redirects me to azure.

I registered the domain on azure
Sai Prasanna Sinde 5,240 Reputation points Microsoft External Staff

2025-03-27T16:27:33.8466667+00:00

Hi @juan bodniza

As documented here, Azure DNS is not a domain registrar. Azure DNS allows you to host a DNS domain and manage the DNS zone records.

To host your domain in Azure, the zone must be created in Azure and delegated to Azure's authoritative DNS servers with a domain registrar.

You need to update the latest Azure name servers with your domain registrar to ensure proper DNS propagation and name resolution.

Since the issue occurs when logging into your domain registrar's account, please reach out to their support team for assistance in resolving it.

Answer 1

Hello juan bodniza

As discussed, recreating the DNS zone was able to propagate the DNS globally with below nameservers.

ns1-04.azure-dns.com
ns2-04.azure-dns.net
ns3-04.azure-dns.org
ns4-04.azure-dns.info.

When we performed the nslookup amd Digweb Interface we are able to resolve the DNS records created under the Domain to "t*****".com.

b7quucqv

Kindly let us know if the above helps 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.

Share via

Azure managed domain, and dns not propagating

0 additional answers

Your answer