Can't add or use Azure Static Web App with custom domain

Tuukka 0 Reputation points
2023-12-08T08:28:00.6333333+00:00

Hi,

Adding custom domain name for my Static Web App fails.

I have acquired Azure App Service domain with DNS Zone:

domain name: xn--shkprssi-0za6pb.com

On the Static Web App Custom domains I select the domain on Azure DNS:

User's image

This operation crashes with this error

User's image

When I try to create a TXT ownership validation it also crashes with error

User's image

Earlier I have been trying to add another domain xn--prssishk-5za8oi.live

That also failed with exactly identical error

User's image

The domain names contains scandinavian special characters ä and ö and that is the reason why the domain name is in punycode format which is a representation of Unicode with the limited ASCII character subset.

My domain plain text would be: sähköpörssi.com

Is it possible to do something about this issue? Only other option is to change to another web dev technology. I would like to use Azure Static Web Apps.

Azure Static Web Apps
Azure Static Web Apps
An Azure service that provides streamlined full-stack web app development.
{count} votes

1 answer

Sort by: Most helpful
  1. SnehaAgrawal-MSFT 22,721 Reputation points Moderator
    2023-12-08T13:17:19.7633333+00:00

    @Tuukka

    Thanks for reaching here! This is known and unsupported type of domains causing unpredictable behavior.

    Work-around solution: To do the configuration with a new domain (without special symbols/letters) and it's recommended to avoid domains with special characters as they often confuse the algorithms not only in your hosting or registrar settings, but also those related to searches on a global scale.

    Hosting a site with a new domain, without special characters would help in resolving the issue.

    Please let us know if you have further questions on this.

    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.