App Service Domain delegation to Azure DNS fails with DomainResellerWebService_INVALID_BODY

Question

Hi,

I'm trying to fix an issue where my Azure Static Web App is unreachable via its custom subdomain

Background:

1. My App Service Domain was previously configured to use my Azure DNS Zone located in my resource group.

On April 26th, 2025, Azure Change Analysis shows a change initiated by "System" that reverted the App Service Domain's dnsType from AzureDns to DefaultDomainRegistrarDns. This removed the link to my Azure DNS Zone (dnsZoneId became null) and changed the Name Servers back to the defaults (nsXX.domaincontrol.com).

1. As a result, the App Service Domain status is now "Parked", and my Static Web App custom domain is unreachable (ERR_NAME_NOT_RESOLVED).

So I'm trying to re-delegate the App Service Domain back to use my existing Azure DNS Zone

Problem Encountered:

When I go to the mydomain.com App Service Domain resource in the Azure portal, click "Manage DNS records", and then click the "Delegate to Azure DNS zone" button (selecting the correct subscription, resource group, and the existing mydomain.com DNS zone), the operation fails after a short time.

The Activity Log for the mydomain.com App Service Domain shows a failed "Add or Update Domain" operation with the following error:

Error code: DomainResellerWebService_INVALID_BODY

Status: Failed / BadRequest

Message/Properties: {"Code":"DomainResellerWebService_INVALID_BODY","Message":null,"Target":null,"Details":[{"Message":null},{"Code":"DomainResellerWebService_INVALID_BODY"},{"ErrorEntity":null}],"Innererror":null}

Correlation ID: 7b7e8972-58f1-4abc-9350-ca677cf8c42c (From an attempt around Mon Apr 28 2025 12:33:34 GMT-0700)

Troubleshooting Steps Taken:

• Verified the target Azure DNS Zone exists and appears healthy.
• Verified the necessary CNAME record (subdomain -> my-static-app-default-hostname.azurestaticapps.net) exists within the Azure DNS Zone.
• Waited significant time (30+ minutes) and retried the "Delegate to Azure DNS zone" operation multiple times, consistently getting the same DomainResellerWebService_INVALID_BODY error.
• Checked Azure Service Health - no relevant issues detected.
• Checked domain properties for locks - none visible in the portal.Problem Encountered: When I go to the mydomain.com App Service Domain resource in the Azure portal, click "Manage DNS records", and then click the "Delegate to Azure DNS zone" button (selecting the correct subscription, resource group, and the existing mydomain.com DNS zone), the operation fails after a short time. The Activity Log for the mydomain.com App Service Domain shows a failed "Add or Update Domain" operation with the following error:
  • Error code: DomainResellerWebService_INVALID_BODY
  • Status: Failed / BadRequest
  • Message/Properties: {"Code":"DomainResellerWebService_INVALID_BODY","Message":null,"Target":null,"Details":[{"Message":null},{"Code":"DomainResellerWebService_INVALID_BODY"},{"ErrorEntity":null}],"Innererror":null}
  • Correlation ID: 7b7e8972-58f1-4abc-9350-ca677cf8c42c (From an attempt around Mon Apr 28 2025 12:33:34 GMT-0700)
  Troubleshooting Steps Taken:
  • Verified the target Azure DNS Zone (mydomain.com in myResourceGroup) exists and appears healthy.
  • Verified the necessary CNAME record (subdomain -> my-static-app-default-hostname.azurestaticapps.net) exists within the Azure DNS Zone.
  • Waited significant time (30+ minutes) and retried the "Delegate to Azure DNS zone" operation multiple times, consistently getting the same DomainResellerWebService_INVALID_BODY error.
  • Checked Azure Service Health - no relevant issues detected.
  • Checked domain properties for locks - none visible in the portal.

Please help thanks

Answer 1

Hi Alex,

Please use instructions below to access Domain Control Center (DCC) for your App Service Domain.

1. Navigate to below link, enter contact email listed on your App Service Domain -- Domain Management -- Advanced management (preview) blade , and click Continue:

https://dcc.secureserver.net/account/retrieve

2. A one-time use PIN will be sent to your domain's contact email, enter it on the screen and click Verify Code

Your username(s) will be displayed. Make note of the username. If there are multiple usernames displayed, you can use process of elimination to remove known usernames/customer#s for other GoDaddy accounts you may have.

3. Next you need to reset your password. Please navigate to below link:

https://dcc.secureserver.net/account/reset

In box, enter your GoDaddy username/customer# from previous Retrieve username screen and click Continue:

It should show the contact email obfuscated with message saying it sent password reset link:

Please click link in that email and reset password:

4. Now that you have successfully reset your password, please navigate to below link to sign in, entering your GoDaddy username/customer# and new password:

https://dcc.secureserver.net/domains

You should now see Domain Portfolio tab. If you see blank screen with only Azure in upper left or similar screen that doesn't make sense, open Guest browser session and navigate to the above url and sign-in again.

To open Guest browser session in Chrome you click on little person icon in upper right corner --> Open Guest profile. For Edge you click on little person icon in upper left corner --> Other profiles --> Browse as guest.

NOTE: From this point on things are less predictable, because I don't know why your name servers were switched back to GoDaddy default. There may be message(s) displayed saying there is problem with your domain, and/or when you attempt to change name servers back to Azure it may block you with error. Hopefully if there is an issue you can resolve it without having to contact GoDaddy customer support.

5. Click on the context menu (three dots), then click Edit nameservers.

Next you will edit screen so that it is set to the correct four name servers as shown on your Azure DNS zone for your App Service Domain in Azure portal. Open Azure portal in separate browser tab so you can copy/paste over each name into the Edit nameservers screen, similar to below:

After saving there will be a delay before changes reflect globally.

As I mentioned above, depending on what is wrong with your domain you may be blocked from making changes to the list of DNS servers until you resolve the issue.

Please reply back with your results, whether positive or negative, by adding comment below.

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

Thanks.

-TP