Create a DNS ZONE fail

Question

Create a DNS ZONE fail

Steve B 0

i had an app service domain, which had been working well and had an associated dns zone, but for some reason the dns zone and the app service domain became disconnected. When in the app service domain it said "Link to Azure DNS" which wanted to start a new one it seemed. So i exported the old dns, and deleted it, ( It wasnt propogated anyway ) when i went back to create the new one via the app service domain it said that everything had been assosicated correctly but failed at the end with a GET service not found. I think this was after it created it, it the checked to see if it could open it?

exact error

Fail to perform GET operation on DNS zone.

Error while fetching zone information, error code: ResourceNotFound , Details: The Resource 'Microsoft.Network/dnszones/DOMAINHERE' under resource group 'Development' was not found. For more details please go to https://aka.ms/ARMResourceNotFoundFix.

Steve B 0 Reputation points

2025-11-04T19:45:01.52+00:00

Its looking under resource group Development, but it should be under HOMESMART which is what the app is
Steve B 0 Reputation points

2025-11-04T19:51:38.0533333+00:00

i also just tried to move the resourse group just for the dns zone if it was looking in the wrong area, which said happened successfully but is still in the wrong group, so something is wrong here and its confusing me.
Venkatesan S 925 Reputation points Microsoft External Staff Moderator

2025-11-04T23:08:56.3233333+00:00
Hi Steve B

Thanks for reaching out to Microsoft Q&A.

The issue occurs because the App Service Domain (ASD) and its associated Azure DNS Zone became disconnected after the original zone was deleted or moved to a different resource group.

When you select Link to Azure DNS from the App Service Domain blade, Azure automatically creates (or attempts to retrieve) the DNS zone in the same resource group as the ASD resource itself not in the resource group where your App Service is hosted.

In your case, the ASD resides in the Development resource group, but the App Service is in HOMESMART. After deleting the old zone, the ASD retained an internal reference (dnsZoneId) pointing to the now-missing zone under Development. When the portal performs a final GET operation to verify the zone, it fails with:

Fail to perform GET operation on DNS zone.

This is expected behavior: moving or deleting only the DNS zone does not update the ASD’s internal link. The portal will continue looking in the ASD’s original resource group.

Option 1: Move the App Service Domain

Verify the ASD’s current resource group

Open the App Service Domain in the Azure Portal.

Go to Overview → confirm Resource group = Development.

Move the ASD to the target resource group.

Select the domain → Move → Move to another resource group.

Set Target resource group = HOMESMART.

Click Validate first (resolves locks, policies, or child resources like certificates).

Commit the move. Wait 2–5 minutes for completion.

Re-link to Azure DNS

Return to the ASD blade → Manage DNS records → Link to Azure DNS.

The zone will now be created in HOMESMART, and the dnsZoneId property is updated automatically.

Option 2: Manual DNS Zone Creation and Delegation.

Create a new DNS zone manually in your desired resource group.
az network dns zone create --resource-group HOMESMART --name yourdomain.com

From the DNS zone’s copy the 4-name server (NS) values.

Go to the App Service Domain’s Advanced Management Portal (GoDaddy) and manually update the nameservers to match those from Azure DNS.

Wait for DNS propagation (typically 30–60 minutes), then re-add your records (A, CNAME, TXT, etc.) in the new DNS zone.

Reference:

Move Azure resources to a new resource group or subscription - Azure Resource Manager | Microsoft Learn

Buy and configure an App Service domain - Azure App Service | Microsoft Learn

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.

1 answer

Your answer

Steve B 0 Reputation points

2025-11-04T19:45:01.52+00:00

Its looking under resource group Development, but it should be under HOMESMART which is what the app is
Steve B 0 Reputation points

2025-11-04T19:51:38.0533333+00:00

i also just tried to move the resourse group just for the dns zone if it was looking in the wrong area, which said happened successfully but is still in the wrong group, so something is wrong here and its confusing me.

Answer 1

Hi Steve B
Your App Service Domain was previously connected to an Azure DNS zone. However, the DNS zone and domain became disconnected, and the portal displayed the message “Link to Azure DNS.” When you tried to create a new DNS zone through the App Service Domain, the process seemed to complete but ultimately failed at the last step with an error.

Before creating the zone, please check if there is already a DNS zone with the same name in any resource group. If you do not find one, try creating a new DNS zone manually with that name.
Once the zone is created, you can link the domain in your app service configuration. Make sure you have the necessary permissions before proceeding. Also, check tools like https://www.digwebinterface.com/ and https://mxtoolbox.com/ to see if there are any existing records for this domain.
If your domain is hosted by a third party, please verify if it is delegated to any Azure name servers.

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.

Share via

Create a DNS ZONE fail

1 answer

Your answer