Replies: 1 comment 5 replies
-
If you type a unicode name into your browser, it will not go out and do UTF-8 queries, it will use Punycode. Why do you want to put UTF-8 in your database? |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
i tried to add a new Zone on Endpoint POST /api/v1/servers/localhost/zones with a body
{"name": "büro.de.", "kind": "Native", "masters": [], "nameservers": ["ns1.example.org.", "ns2.example.org."]}
But the Server returns (HTTP Status 422 Unprocessable Entity)
{ "error": "Name 'b\\195\\188ro.de.' contains unsupported characters" }
further i tried to add it with the encoding inside: (same result)
{"name": "b\\195\\188ro.de.", "kind": "Native", "masters": [], "nameservers": ["ns1.example.org.", "ns2.example.org."]}
The interesting thing is you can create such zones with
`pdnsutil create-zone``
and you can even read them with the Endpoint GET /api/v1/servers/localhost/zones/büro.de.
I was wondering if there is a way to create zones with the API including UTF-8 characters.
I also found this issue with some similar issue but on another Endpoint #12725
Does the stricter validation also apply here? and why is it even stricter?
Beta Was this translation helpful? Give feedback.
All reactions