Upstream DNS servers do not support Chinese domain names

[banbendalao]

Have a question or an idea? Please search it on our forum to make sure it was not yet asked. If you cannot find what you had in mind, please submit it here.

Prerequisites

Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

• I am running the latest version
• I checked the documentation and found no answer
• I checked to make sure that this issue has not already been filed

Issue Details

• Version of AdGuard Home server:
  v0.106.0-a.95+2a435601
• How did you install AdGuard Home:
  Github releases
• How did you setup DNS configuration:
  System
• If it's a router or IoT, please write device model:
• CPU architecture:
  AMD64
• Operating system and version:
  Debian10

Expected Behavior

Support Chinese domain names

Actual Behavior

Fill in Upstream DNS servers
[/恒天.com/]223.5.5.5
Will not be able to start AdGuardHome

[ainar-g]

This is a bug, thanks for reporting! In the meantime, please try using the punycode version:

[/xn--rss99n.com/]223.5.5.5

[Aikatsui]

@ainar-g related issue,
https://en.wikipedia.org/wiki/List_of_Internet_top-level_domains#Internationalized_country_code_top-level_domains
https://en.wikipedia.org/wiki/List_of_Internet_top-level_domains#Internationalized_generic_top-level_domains

Currently UI (including query log) display only punnycode for language specific domain names and extensions, it makes uncomfortable due necessary to use converter for recognize them and as russian characters more familiar to you than english then i believe each script especially beneficial for particular users.
But users may fail to recognize eg: latin script uses languages (between english and spanish) domain names properly then it's better to add "punnycode" field to "request details" component.

[ainar-g]

@Aikatsui, thanks for the requests. I've filed #3012 for the backend part about the search and also #3013 for the frontend part about showing decoded domain names.

[fernvenue]

@Aikatsui, thanks for the requests. I've filed #3012 for the backend part about the search and also #3013 for the frontend part about showing decoded domain names.

Actually this issue still exists in upstream_dns_file, please check it again, thank you so much.

[ainar-g]

@fernvenue, this issue isn't closed yet, so we know it still exists. Unfortunately, the issue spans multiple packages, so we won't be able to fix it as quickly as we would like.

[fernvenue]

@fernvenue, this issue isn't closed yet, so we know it still exists. Unfortunately, the issue spans multiple packages, so we won't be able to fix it as quickly as we would like.

Thank you for letting me know, I'll wait patiently and keep paying attention. Perhaps it's a good idea to comment this in the configuration at the moment? Because #3013 the frontend part of the display decoding domain is normal, this may make people mistakenly think that it works normally in upstream_dns_file.

[ainar-g]

@fernvenue, thanks for the suggestion and sorry about the late response. We've mentioned the bug on the wiki page about configuration: https://github.com/AdguardTeam/AdGuardHome/wiki/Configuration#upstreams-from-file.