From 7f957b3e8a0009d9b995877b8fe322ee7468bb3e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Christian=20K=C3=B6nig?= Date: Fri, 3 Dec 2021 14:50:53 +0100 Subject: [PATCH] Improve IDN section MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Christian König --- docs/main/faq.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/main/faq.md b/docs/main/faq.md index cc5367d..8a11a19 100644 --- a/docs/main/faq.md +++ b/docs/main/faq.md @@ -49,9 +49,9 @@ During a gravity update, Pi-hole complains about some invalid Internationalized **Solution:** -Internationalizing Domain Names in Applications (IDNA) was conceived to allow client-side use of language-specific characters in domain names without requiring any existing infrastructure (DNS servers, mall servers, etc., including associated protocols) to change. But, the corresponding original [RFC 3490](https://tools.ietf.org/html/rfc3490) clearly states that IDNA is employed at application level, not on the server side. +Ask the list maintainer to convert the IDNs to their punycode representation. + +Internationalizing Domain Names in Applications (IDNA) was conceived to allow client-side use of language-specific characters in domain names without requiring any existing infrastructure (DNS servers, mall servers, etc., including associated protocols) to change. Accordingly, the corresponding original [RFC 3490](https://tools.ietf.org/html/rfc3490) clearly states that IDNA is employed at application level, not on the server side. Hence, DNS servers never see any IDN domain name, which means DNS records do not store IDN domain names at all, only their [Punycode](https://en.wikipedia.org/wiki/Punycode) representations. -Therefore, ask the list maintainer to convert the IDNs to their punycode representation. - {!abbreviations.md!}