On 24.09.2015 09:34, Tomas Hozza via RT wrote:
> On 23.09.2015 19:10, Evan Hunt via RT wrote:
> >
> > On Wed, Sep 23, 2015 at 04:10:42PM +0000, Tomas Hozza via RT wrote:
> >> Works the same way also in the current patch set. However I was
> >> not able to transfer the root zone. So if you can test this,
> >> it would be great.
> >
> > If you use "dig @f.root-servers.net" it should work, it's configured
> > to allow transfer for anyone.
> >
> > (More detailed response to follow when I have a bit more time.)
>
> Thank you for the hint. I retested the code.
>
> With libidn:
> dig @f.root-servers.net axfr .  --> there are domains with Unicode characters in the output
> IDN_DISABLE="" dig @f.root-servers.net axfr .  --> there are no domains with Unicode characters, only xn--
>
> With libidn2:
> dig @f.root-servers.net axfr . --> there are no domains with Unicode characters, only xn--
> IDN_DISABLE="" dig @f.root-servers.net axfr . --> there are no domains with Unicode characters, only xn--
>
> As noted before, the behavior with libidn2 is expected, since
> libidn2 does not support translation from punycode to Unicode.
>
> Thanks!
>
> Regards,
>

Hello.

Fedora plans to move to libidn2 and get completely rid of libidn since Fedora 27 (https://fedoraproject.org/wiki/Changes/IDNA2008).

Rather than carrying another downstream patch in Fedora, we would like to work with you on the inclusion of the functionality into BIND.

Can you please review the last version of patch set we sent to you and let us know in case you need anything from us?

Thank you in advance!

Regards,
-- 
Tomas Hozza
Associate Manager, Software Engineering - EMEA ENG Mainstream RHEL

PGP: 1D9F3C2D
UTC+1 (CET)
Red Hat Inc.                 http://cz.redhat.com