New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NETCUP: Unicode (non-punycode) not supported? #2451
Comments
Just for some context: Same issue has been raised for provider INWX too, with issue #2450 |
Yeah, seemingly there needs to be a decision what the input format for dnscontrol should be. I think Tom's suggestion there is reasonable and would address this issue. |
(I just had this thought... it may be totally wrong but I'll put it out there) Proposal: Domains: The goal should be that the string a user enters in dnsconfig.js should match the string they see in the provider's web portal. That would simplify things for the user, and give us an obvious goal for how the code is supposed to work. Records: The individual records should permit punycode and UTF-8, and be converted to the format that the provider prefers. This could be all UTF-8, all punycode, or a mix (use whatever string is in dnsconfig.js). Would that work? |
One note about "should match the string they see in the provider's web portal". That is not consistent between providers. i.e. I have a domain registered via namecheap which uses the punycode, but DNS is on Cloudflare which uses the UTF-8 representation. |
Related: #2097 |
It seems IDN domains are only supported with punycode format at v4.1.1.
D("exämple.at", …
tries to (re-) create all records and silently fails. (They are not visible at the netcup CCP.)D("xn--exmple-cua.at", …
works as expected./cc @kordianbruck
The text was updated successfully, but these errors were encountered: