CC: undisclosed-recipients: ; MIME-Version: 1.0 In-Reply-To: Content-Disposition: inline References: <215853110.6673989.1401345929725.JavaMail.zimbra@redhat.com> <20140612180030.GA67297@isc.org> <194463002.11114099.1402641552531.JavaMail.zimbra@redhat.com> <20140613072226.GA72946@isc.org> Message-ID: <20140613072424.GB72946@isc.org> Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Received: from bikeshed.isc.org (bikeshed.isc.org [149.20.48.19]) by bugs.isc.org (Postfix) with ESMTP id 074922D20571 for ; Fri, 13 Jun 2014 07:24:25 +0000 (UTC) Received: by bikeshed.isc.org (Postfix, from userid 10292) id EF71A216C31; Fri, 13 Jun 2014 07:24:24 +0000 (UTC) Delivered-To: bind-suggest@bugs.isc.org User-Agent: Mutt/1.4.2.3i Subject: Re: [ISC-Bugs #36101] IDN support in host/dig/nslookup using GNU libidn(2) Return-Path: X-Original-To: bind-suggest@bugs.isc.org Date: Fri, 13 Jun 2014 07:24:24 +0000 To: Evan Hunt via RT From: Evan Hunt RT-Message-ID: Content-Length: 315 > With libidn2, the LANG trick for disabling IDN mentioned in the man page > (LANG=langauage[_terrotory].ASCII) doesn't seem to be working as described; > I'm not sure yet why not. Can you try it out? CHARSET=ASCII not working with libidn, either. In both cases I get: dig: convert textname to UTF-8: failure