Static web app custom domain failed

Question

static web app custom domain failed and made site unreachable. Deleting and recreating has failed several times. Now been down for 2 hrs. Any suggestions. Worst down I have had in years and still no resolution. Now I can't even remove the custom domain to recreate. DNS is godaddy, no recent changes

Answer 1

HI @Fredrik Gjaerdman

Following our discussion, I'm glad to hear that after deleting and re-adding the custom domain, everything is now working correctly.

Issue Summary: The custom domain was stuck due to an internal backend state conflict (common after slice changes and prior certificate activity). Deleting and re-adding with the proper validation method resolved it.

Your site should now be fully accessible

Thank you for your patience throughout this incident. If you notice any further issues or need help with anything else, feel free to reach out anytime.

Answer 2

Next step is to remove the Static Web App and rewire the app to see it this helps

Answer 3

Have now had 15 hours of downtime which is a record in the last 10 years. Still no solution to this problem. Creation of any custom domains fails with "unknown error". The domain in question is clean, godaddy hosted, no CAA records. Static Web App log confirms Validation succeeds but UI says Validation failed.

Answer 4

Hi @Fredrik Gjaerdman

Thank you for reaching us regarding the issue.

Azure Static Web Apps provides free SSL/TLS certificates for custom domains, and each custom domain can only be bound to a single resource. If you attempt to bind a domain that is already associated with another resource or is in a conflicting state, the operation will fail. Additionally, some domain registrars, such as GoDaddy, do not fully support the DNS records required for apex (root) domains, including ALIAS or ANAME records or reliable CNAME flattening. In such cases, Microsoft recommends hosting your domain zone in Azure DNS to ensure better compatibility and reliable global DNS distribution.

Setup and Management Recommendations

• For subdomains (e.g., www): Configure a CNAME record pointing to your app's default hostname (*.azurestaticapps.net).
• For apex domains: Use supported records (ALIAS/ANAME where available) or fall back to an A record (not recommended for global traffic, as it limits Azure’s edge distribution).
• Validation requires the domain to be publicly resolvable. DNS changes must propagate before full functionality (including certificate issuance).

Handling Issues (Removal and Reconfiguration)

The documentation emphasizes proper disassociation:

• Before re-adding or migrating a domain, fully remove it from any previous binding.
• If migrating between Static Web Apps (or instances in the same slice), first remove the domain from the original resource. This may involve some downtime.

Recommended Actions:

• Remove conflicting DNS records at your provider (GoDaddy) to allow clean disassociation.
• In the Azure portal, navigate to your Static Web App > Custom domains and attempt to delete the problematic domain.
• Wait for propagation and backend updates (DNS and Azure operations can take time).
• Once cleared, re-add the custom domain following the external provider steps, starting with ownership validation.
• If using GoDaddy, strongly consider migrating the DNS zone to Azure DNS for apex domain support.

Reference:
https://learn.microsoft.com/en-us/azure/static-web-apps/custom-domain

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

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