Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
X-RT-Original-Encoding: utf-8
Content-Length: 1174

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