Comment 5 for bug 1918654

Here is the output:
$ dig 人民网.中国

; <<>> DiG 9.11.27-RedHat-9.11.27-1.fc33 <<>> 人民网.中国
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62795
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;人民网.中国. IN A

;; ANSWER SECTION:
人民网.中国. 7198 IN A 58.68.146.208

;; Query time: 3731 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Mar 15 08:38:30 PDT 2021
;; MSG SIZE rcvd: 70

Or

dig 人民网.中国

; <<>> DiG 9.16.1-Ubuntu <<>> 人民网.中国
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29429
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;人民网.中国. IN A

;; ANSWER SECTION:
人民网.中国. 6787 IN A 58.68.146.208

;; Query time: 0 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Mar 15 15:45:21 UTC 2021
;; MSG SIZE rcvd: 70

The problem I have here is we are inconsistent in our API usage of UTF-8. JSON is UTF-8, the documentation lists that we return UTF-8 content, the API accepts and handles UTF-8 strings for other fields such as the description fields, and by the RFCs TLDs support UTF-8.
I think this can be corrected in designate in a way that does not break existing usage, but we need to embrace other cultures and languages.