# Experience report: IDN domain name

**URL:** https://meta.discourse.org/t/experience-report-idn-domain-name/393882
**Category:** Self-hosting
**Tags:** domains
**Created:** [January 20, 2026, 1:09pm UTC](https://meta.discourse.org/t/experience-report-idn-domain-name/393882 "2026-01-20T13:09:44Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![John\_Platte](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/john_platte/32/529465_2.png) [@John\_Platte](https://meta.discourse.org/u/John_Platte)
#### Post date: [January 20, 2026, 1:09pm UTC](https://meta.discourse.org/t/experience-report-idn-domain-name/393882/1 "2026-01-20T13:09:44Z")

</div>

I’m self-hosting a Discourse instance and just switched to an internationalized domain name (non-Latin characters). Wanted to share a couple items that made this bumpier than needed:

First: [ask.discourse.com](http://ask.discourse.com) incorrectly told me to use the Unicode version of the name in app.yml, but this caused Let’s Encrypt to need the `idn` package installed in the container, and then resulted in a redirect loop since my browser requested the Punycode version of the name and Discourse kept redirecting to the Unicode.

Then, more minor, but more visible after things are working: Discourse ID prints out the Punycode version of the name on screen in its announcement that it’s going to redirect. It would be more reassuring to users not to have that happen.
