Azure Domains – Unable to Update Nameservers After Recreating DNS Zone

intellectuable 0 Reputation points
2025-03-04T21:06:37.2633333+00:00

I am facing an issue with my domain, which i manage through Azure Domains.

Recently, i deleted and recreated my azure DNS Zone, and new nameservers were assigned. However, WHOIS still shows the old nameservers, and my DNS changes are not propagating.

I suspect the status clientUpdateProhibited is preventing the update from being sent to the ICANN root servers. Unfortunately, i cannot find an option to unlock the domain from Azure Portal.

I made changes two days ago.

New nameserver:

User's image

Current Whois:

Current Whois

Do you have an idea how to force an ICANN name server update ?

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

1 answer

Sort by: Most helpful
  1. TP 108.7K Reputation points
    2025-03-04T22:11:11.39+00:00

    Hi,

    First, this is happening because you deleted your Azure DNS Zone for your App Service Domain. Deleting the DNS Zone breaks DNS resolution. Creating a new zone didn't fix it, because the new zone wasn't placed on the same Azure DNS servers.

    Second, I have a script that gives you full access to your GoDaddy Domain Control Center (DCC) which allows you to make any/all changes to your domain, similar to a regular GoDaddy customer.

    Unfortunately, my script relies on generateSsoRequest REST API which stopped working several months ago (back in 2024). You can try the REST API yourself and see if they fixed it using the "Try it" button. If it is fixed I would be happy to post my script.

    The manual way you can fix your domain is to repeatedly delete/re-create your Azure DNS Zone until it is placed on the correct DNS servers. From your screenshot the correct DNS servers are:

    • Name Server: NS1-35.AZURE-DNS.COM
    • Name Server: NS2-35.AZURE-DNS.NET
    • Name Server: NS3-35.AZURE-DNS.ORG
    • Name Server: NS4-35.AZURE-DNS.INFO

    This is your goal--to have the DNS Zone land on 35. There are 47 (1-47). You can carefully create the Zone, check which servers it landed on, delete it if it isn't on correct servers, create it again, etc.

    NOTE: Azure DNS is not free. There is small cost for each zone per month, plus the number of queries (this isn't a concern in this case). I forget the minimum granularity it bills the zones at. For example, if it bills for minimum one hour and you have to create/delete a total of 100 times, then the total cost would be minimal. If the minimum is 1 month, then the cost could add up. Of course you could dispute and they would likely refund since it is same domain name.

    Please let me know if the above isn't clear.

    Please click Accept Answer and upvote if the above was helpful.

    Thanks.

    -TP


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.