dnscontrol: INWX: Punycode not supported?

It seems IDN domains are only supported without punycode format at v4.1.1.

D("xn--exmple-cua.at", … throws an error at dnscontrol push:

WARNING: Error creating domain: (2302) Object exists. Reason: (Error_DomainAlreadyInDNS) The domain is already in the DNS.

Only D("exämple.at", … works. I think this is not the intended behavior?

/cc @patschi

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 16 (10 by maintainers)

Most upvoted comments

Confirmed, fixed. Thanks!

The fix for the “2302 Object exists”/“DomainAlreadyInDNS” API error when pushing changes to an IDN zone was included in v4.19.0. I believe this issue can be closed.

PR https://github.com/StackExchange/dnscontrol/pull/3519 resolves the FAILURE (2302) Object exists... issue with IDN domains in my testing.

I would say this RFC covers the “opinions” about how IDN should be handled in applications. https://datatracker.ietf.org/doc/rfc3490/

More about IDN can be found by this author: https://datatracker.ietf.org/person/paf@paftech.se

DNSControl is an opinionated system. Is there an “opinion” about how IDN domains should be handled that would help?

(I don’t own any such domains and have nearly zero experience here)

I’m not an expert when it comes to encoding, like punycode/unicode or what amplifications it might have.

My high-level thought: As dnscontrol is designed to be managed by users (manually), showing the exämple.at-representation is the better, more user-friendly approach. That’s what we could/should use primarily in the dnscontrol code base, and also shown at preview/push accordingly.

Depending on the provider and its API, we might then decide (a new capability flag for it?) if a special processing is needed - like converting to/from punycode before interacting with the API.