I'm trying to add a custom domain to my static web app

Question

I'm trying to add a custom domain to my static web app

Pavlin Penev 0

Hello,

I'm trying to add a custom domain to my static web app but it throws an error.
User's image

As you can see the image I'm trying to add this domain to the www subdomain. I can confirm that the DNS record for validating the domain ownership is indeed set in my provider and more than 12 hours have passed since then.

Can you advice on what the issue would be?

Thank you in advance!

Siva Nair 2,340 Reputation points Microsoft External Staff Moderator

2025-06-16T21:21:19.24+00:00
Hi Pavlin Penev,

Although 12 hours is usually enough, DNS changes can sometimes take longer to propagate depending on your DNS provider. You can check the propagation status using tools like WhatsMyDNS.net to ensure that your DNS records have propagated correctly across the globe.

Make sure that the CNAME record for the 'www' subdomain is correctly pointing to the Azure static web app. It should look something like this:

Type: CNAME

Name: www

Value: your-static-web-app-name.azurestaticapps.net

Ensure that your DNS provider's configuration matches the required settings for Azure. Sometimes, issues arise from incorrect record types or values.

If SSL is enabled on your custom domain, ensure that the SSL certificate has been issued correctly.

Check if there are any notifications in the Azure portal related to your static web app that might hint at what's going wrong.

If you have any further assistant, do let me know.
Pavlin Penev 0 Reputation points

2025-06-17T06:31:12.2166667+00:00
Hello Siva,

Thank you for your quick reply!

To summarize on your instructions:

I can safely say that the DNS record was set on the 13th so I am positive that more than the 12 hours have passed. And also the propagation has finished globally.

As far as my past experience go, we should first pass validation of domain ownership and insert the CNAME record after. The error is on the validation step during inserting the TXT record. Advice if we should insert the CNAME record beforehand, thank you.

No DNS record mismatches.

SSL has been issued correctly.

Sadly, no hints on what would the error be. I'm open to any advice here on where should I check.

Thank you for your support!
Siva Nair 2,340 Reputation points Microsoft External Staff Moderator

2025-06-18T15:58:02.38+00:00

Hi Pavlin Penev,

Just checking back if the above response was helpful, if you have any questions or concerns please, feel free to post back.

Thanks
Siva Nair 2,340 Reputation points Microsoft External Staff Moderator

2025-06-20T19:15:41.8966667+00:00

Hi Pavlin Penev,

Just checking back if the above response was helpful, if you have any questions or concerns please, feel free to post back.

Thanks
Pavlin Penev 0 Reputation points

2025-06-23T06:29:31.2833333+00:00

Hello Siva,

Sorry for the belated reply. Yes, we managed to fix the issue. We deleted the set custom domain, the already set TXT record and re-added it using CNAME directly and it validated. Thank you for your support!

Kind Regards

1 answer

Your answer

Siva Nair 2,340 Reputation points Microsoft External Staff Moderator

2025-06-16T21:21:19.24+00:00

Hi Pavlin Penev,

Although 12 hours is usually enough, DNS changes can sometimes take longer to propagate depending on your DNS provider. You can check the propagation status using tools like WhatsMyDNS.net to ensure that your DNS records have propagated correctly across the globe.

Make sure that the CNAME record for the 'www' subdomain is correctly pointing to the Azure static web app. It should look something like this:

Type: CNAME

Name: www

Value: your-static-web-app-name.azurestaticapps.net

Ensure that your DNS provider's configuration matches the required settings for Azure. Sometimes, issues arise from incorrect record types or values.

If SSL is enabled on your custom domain, ensure that the SSL certificate has been issued correctly.

Check if there are any notifications in the Azure portal related to your static web app that might hint at what's going wrong.

If you have any further assistant, do let me know.
Pavlin Penev 0 Reputation points

2025-06-17T06:31:12.2166667+00:00

Hello Siva,

Thank you for your quick reply!

To summarize on your instructions:

I can safely say that the DNS record was set on the 13th so I am positive that more than the 12 hours have passed. And also the propagation has finished globally.

As far as my past experience go, we should first pass validation of domain ownership and insert the CNAME record after. The error is on the validation step during inserting the TXT record. Advice if we should insert the CNAME record beforehand, thank you.

No DNS record mismatches.

SSL has been issued correctly.

Sadly, no hints on what would the error be. I'm open to any advice here on where should I check.

Thank you for your support!
Siva Nair 2,340 Reputation points Microsoft External Staff Moderator

2025-06-18T15:58:02.38+00:00

Hi Pavlin Penev,

Just checking back if the above response was helpful, if you have any questions or concerns please, feel free to post back.

Thanks
Siva Nair 2,340 Reputation points Microsoft External Staff Moderator

2025-06-20T19:15:41.8966667+00:00

Hi Pavlin Penev,

Just checking back if the above response was helpful, if you have any questions or concerns please, feel free to post back.

Thanks
Pavlin Penev 0 Reputation points

2025-06-23T06:29:31.2833333+00:00

Hello Siva,

Sorry for the belated reply. Yes, we managed to fix the issue. We deleted the set custom domain, the already set TXT record and re-added it using CNAME directly and it validated. Thank you for your support!

Kind Regards

Answer 1

Hi Pavlin Penev,

solution by pavlin - Yes, we managed to fix the issue. We deleted the set custom domain, the already set TXT record and re-added it using CNAME directly and it validated.

You're absolutely right that the domain ownership validation step comes first, and the CNAME should only be added after successful validation. Since the error is occurring during the TXT record validation, here are a few things we can double-check to help move this forward:

TXT Record Name Format For a www subdomain, Azure typically expects the TXT record name to be: asuid.www Please ensure that your DNS provider hasn’t automatically appended the domain name (e.g., asuid.www.example.com), which can cause validation to fail.
TXT Record Value Double-check that the value matches exactly what Azure provided — no extra quotes, spaces, or formatting changes.
DNS Lookup Confirmation You can use a tool like https://toolbox.googleapps.com/apps/dig/ to confirm the TXT record is publicly visible. Just run: dig TXT asuid.www.example.com
Azure Cache or Stale Validation If everything looks correct, try removing the domain from Azure, waiting 10–15 minutes, and then re-adding it. This can help clear any cached validation attempts.

If you have any further assistant, do let me know.

Share via

I'm trying to add a custom domain to my static web app

1 answer

Your answer