On 01/11/2015 01:10 PM, Mukund Sivaraman via RT wrote:
> Hi Tomas
>
> On Mon, May 26, 2014 at 12:51:54PM +0000, Tomas Hozza via RT wrote:
> > We maintain like 5 Fedora/RHEL specific patches that are modifying
> > host/dig/nslookup to use libidn instead of idnkit.
>
> This is somewhat related, but because we don't maintain these patches in
> the BIND tree yet, I'm mentioning it here instead of creating an ISC
> bug:
>
> Run Wireshark and try the following query in nslookup:
>
> ra4add\226a\2384Cohd\191\222\2384Cohd\191\222\2384Cohd\191\222\2384Cohd\191\222\2384Cohd\191\222\2384Cohd\191\222\2384Cohd.\191\222\2384Cohd\191\222\2384Cohd\191\222\2384Cohd\191\222\2384Cohd\191\222\2384Cohd\191\222\2384Cohd\191\222\2384Cohd\191.\222\2384Cohd\191\222\2384Cohd\191\222\2384Cohd\191\222\2384Cohd\191\222\2384Cohd\191\222\2384Cohd\191\222\2384Cohd\191\222.\2384Cohd\191\222\2384Cohd\191\222\2384Cohd\191\222\2384Cohd\191\222\2384Cohd\191\222\2384Cohd\191\222\2384Cohd\191\222\238.4Co.example.org
>
> Repeat it a few times. It seems there is some misbehavior due to the
> patches to BIND in Fedora (probably libidn related) that causes it to
> send junk names (random every time). Vanilla BIND with and without
> idnkit configured don't show this issue.
>
>         Mukund
>
Hi Mukund.

Thanks for the notice. There sure may be some issue related to those downstream patches. They were created long time ago.

The work on the patches is still in my TODO. I haven't yet resolved issues catches by Evan. The work on IDN had low priority in the past few months.

I'll make sure to look at the issue you're describing before sending a new patch.

Regards,
-- 
Tomas Hozza
Software Engineer - EMEA ENG Developer Experience

PGP: 1D9F3C2D
Red Hat Inc. http://cz.redhat.com