App Service Domain nameservers changed to GoDaddy defaults - website down, cannot reset to Azure DNS

To reset the nameservers back to Azure DNS for your domain purchased through Azure App Service Domains, you can follow these steps:

1. Check Azure Portal: Ensure that your domain is correctly listed in the Azure Portal under App Service Domains. Verify that the nameservers shown in the domain properties are indeed the Azure DNS nameservers.
2. Use Azure DNS Management: Since you mentioned that the Azure Portal does not provide an option to change nameservers directly, you may need to use the Azure REST API or Azure CLI to manage your DNS settings.
   • You can try using the Azure CLI command to set the nameservers back to Azure DNS. The command would look something like this:

          az network dns zone update --resource-group <your-resource-group> --name <your-domain-name> --set nameServers=<ns1>,<ns2>,<ns3>,<ns4>
     

   • Replace <your-resource-group> with the name of your resource group and <your-domain-name> with your actual domain name. The <ns1>, <ns2>, <ns3>, and <ns4> should be replaced with the Azure DNS nameservers you provided.
3. Contact Azure Support: If you continue to face issues with the REST API or CLI commands, it may be necessary to contact Azure Support for assistance. They can help you restore the nameservers to Azure DNS and resolve any underlying issues with your domain.
4. Verify DNS Propagation: After making changes, use a DNS propagation checker tool to verify that the nameservers have been updated correctly and that your website is back online.

By following these steps, you should be able to reset your nameservers back to Azure DNS and restore your website functionality.

References:

• Migrate an existing domain to Azure App Service
• Use Azure DNS to provide custom domain settings for an Azure service
• Buy and manage an App Service domain

The AI answer does not solve my issue.

The Azure DNS Zone nameservers are already correct:

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

The problem is at the REGISTRAR level. When I run dig NS topikbuddy.com, it returns:

• ns47.domaincontrol.com
• ns48.domaincontrol.com

These are GoDaddy's default nameservers, not Azure DNS.

The domain was purchased through Azure App Service Domains (which uses GoDaddy as backend). I cannot access GoDaddy

directly to change the nameservers - the domain doesn't appear in my GoDaddy account.

I need help changing the nameservers at the REGISTRAR level, not the DNS zone level. Is there an API or method to

update the registrar nameservers for an App Service Domain?

Hi @Tergel Munkhbat

Thank you for the thorough follow-up and for sharing the dig output. This appears to be a typical registrar-level mismatch, where the authoritative nameservers have switched back to GoDaddy's defaults (ns47/ns48.domaincontrol.com) following the dnsType change, despite Azure displaying everything correctly.

You’re correct that using self-service options like the REST API (to update dnsType/dnsZoneId) or portal tools won’t update the registrar backend. App Service Domains are registered through GoDaddy, and Azure doesn’t provide direct access to manage nameservers at the registrar for these domains.

Official docs confirm this integration and the managed nature:

• App Service domains use GoDaddy for registration and Azure DNS for hosting:
  https://dori-uw-1.kuma-moon.com/en-us/azure/app-service/manage-custom-dns-buy-domain
• DNS records are fully manageable in Azure, but registrar operations (including nameserver delegation fixes when stuck) are automated/hand-led internally.

The most reliable way to address this issue is by contacting Azure Support. They have access to the GoDaddy reseller channel and can manually re-sync or reset the registrar nameservers to Azure's (such as ns1-04.azure-dns.com, etc.).

To get it sorted quickly:

1. In the Azure Portal, go to Help + support > New support request.
2. Issue type: Technical > Service: App Service > Problem type: Domain Registration.
3. Include your domain (topikbuddy.com), current NS from dig, desired Azure NS, and mention the accidental dnsType change via API that triggered the fallback.

Support can usually handle this backend reset within a day or two, and once done, propagation should bring your site back online.

For more on creating support requests: https://dori-uw-1.kuma-moon.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request

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

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

Thanks @TP and @Praneeth for the technical details.

To be honest, this experience has been a dealbreaker. The fact that I cannot manage basic nameservers for a domain I own without paying for a 'Technical Support' plan ($29/month) or running complex PowerShell commands is unacceptable for a startup.

I have decided to abandon this domain and purchase a new one from a registrar that provides full DNS control out of the box. It is faster and cheaper for me to buy a new domain ($10) than to navigate this broken Azure interface or pay $29/month tech support to fix their own bugs.

I am accepting TP's answer because the PowerShell command is likely the only working technical solution, but I strongly advise others to avoid buying domains from Azure App Service Domains.

For example, as of December 2025, the platform instability makes it impossible to move DNS to external providers like Cloudflare (which startups need for security), effectively locking you in.