Share via

Adding a custom domain (managed by GoDaddy) to azure static web app fails even after 48 hrs

Pws Admin 0 Reputation points
2026-04-01T03:05:38.6566667+00:00

We have a domain name managed by GoDaddy. We did create the CNAME in GoDaddy and DNS lookup reflects the change immediately when verified from all DNS lookup tools. But when adding the same from azure side fails. We were tring after 48 hours and still the same. Whereas domains in other DNS providers are kind of working properly. May we know why and is there a way to fix this? The TXT option is also not working and generate button never generates a code

Azure Static Web Apps
Azure Static Web Apps

An Azure service that provides streamlined full-stack web app development.


2 answers

Sort by: Most helpful
  1. Shree Hima Bindu Maganti 7,110 Reputation points Microsoft External Staff Moderator
    2026-04-16T18:17:53.63+00:00

    Hello @Pws Admin
    This behavior is typically due to DNS record conflicts or GoDaddy limitations rather than Azure propagation delay. For a subdomain such as www, Azure Static Web Apps requires a single public CNAME record that points directly to your default Static Web App hostname (for example, yourapp.azurestaticapps.net), with no URL forwarding, masking, A/AAAA records, or duplicate CNAME/TXT records for the same host. Azure validates using public DNS resolvers, so even if GoDaddy shows the record, validation can still fail if stale records, DNSSEC, or forwarding rules are interfering. For an apex/root domain, GoDaddy does not fully support ALIAS/ANAME or CNAME flattening needed for optimal Azure Static Web Apps root-domain mapping, so the recommended approach is to first configure www as a CNAME and then forward the root domain to www, or move DNS hosting to Azure DNS for full support. For TXT validation, Azure should generate the ownership code after selecting TXT and entering the hostname; if the portal does not generate the code, this may be a portal-side issue, so retry in an InPrivate browser session, clear cache, or use Azure CLI/REST as a workaround. Please follow Microsoft’s official guidance for external DNS custom domain setup and apex domain limitations .
    https://learn.microsoft.com/en-us/azure/static-web-apps/custom-domain
    https://learn.microsoft.com/en-us/azure/static-web-apps/apex-domain-external
    Let me know if you have any further assistance needed.

    0 comments No comments

  2. Praneeth Maddali 7,645 Reputation points Microsoft External Staff Moderator
    2026-04-07T11:27:07.11+00:00

    Hello @Pws Admin

    Could you please confirm whether Enterprise-grade edge is enabled for this Static Web App?

    You can check this easily in the Azure portal:

    1. Go to your Static Web App.
    2. In the left menu, click Enterprise-grade edge.
    3. See if the option is checked/enabled.

    Please share a screenshot of that page (or just say Yes/No).

    This is important because:

    • If Enterprise-grade edge is enabled, custom domain validation must use TXT record only (CNAME is not supported).
      User's image
    • If it is disabled, we can proceed with the standard troubleshooting (CAA record + TXT validation).

    reference :

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

    If the answer is helpful,  Please do click "Accept the answer” and Yes, this can be beneficial to other community members.

    If you have any other questions, let me know in the "comments" and I would be happy to help you

    0 comments No comments

Your answer

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