From owner-freebsd-bugs@FreeBSD.ORG Thu Feb 6 14:30:02 2014 Return-Path: Delivered-To: freebsd-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CEFDBC6 for ; Thu, 6 Feb 2014 14:30:02 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A0DE01ADD for ; Thu, 6 Feb 2014 14:30:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s16EU2w0080011 for ; Thu, 6 Feb 2014 14:30:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s16EU2cI080010; Thu, 6 Feb 2014 14:30:02 GMT (envelope-from gnats) Date: Thu, 6 Feb 2014 14:30:02 GMT Message-Id: <201402061430.s16EU2cI080010@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Oliver Fromme Subject: Re: bin/186510: [PATCH] Latest BIND port triggers problem in portsnap X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Oliver Fromme List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Feb 2014 14:30:02 -0000 The following reply was made to PR bin/186510; it has been noted by GNATS. From: Oliver Fromme To: bug-followup@FreeBSD.org Cc: Subject: Re: bin/186510: [PATCH] Latest BIND port triggers problem in portsnap Date: Thu, 6 Feb 2014 15:20:33 +0100 (CET) Addendum: At first I wasn't able to reproduce the problem on a second machine. Then it turned out that it actually depends on the name server being used: $ host -t srv _http._tcp.portsnap.freebsd.org. ns-20.awsdns-02.com. ;; Truncated, retrying in TCP mode. Using domain server: Name: ns-20.awsdns-02.com. Address: 205.251.192.20#53 Aliases: _http._tcp.portsnap.freebsd.org has SRV record 1 10 80 ec2-eu-west-1.portsnap.freebsd.org. _http._tcp.portsnap.freebsd.org has SRV record 2 10 80 sourcefire.portsnap.freebsd.org. _http._tcp.portsnap.freebsd.org has SRV record 2 10 80 your-org.portsnap.freebsd.org. _http._tcp.portsnap.freebsd.org has SRV record 3 10 80 isc.portsnap.freebsd.org. _http._tcp.portsnap.freebsd.org has SRV record 4 10 80 ec2-ap-northeast-1.portsnap.freebsd.org. _http._tcp.portsnap.freebsd.org has SRV record 4 10 80 ec2-ap-southeast-2.portsnap.freebsd.org. _http._tcp.portsnap.freebsd.org has SRV record 4 10 80 ec2-sa-east-1.portsnap.freebsd.org. $ host -t srv _http._tcp.portsnap.freebsd.org. 127.0.0.1 ;; Truncated, retrying in TCP mode. Using domain server: Name: 127.0.0.1 Address: 127.0.0.1#53 Aliases: _http._tcp.portsnap.FreeBSD.org has SRV record 2 10 80 your-org.portsnap.freebsd.org. _http._tcp.portsnap.FreeBSD.org has SRV record 4 10 80 ec2-ap-southeast-2.portsnap.freebsd.org. _http._tcp.portsnap.FreeBSD.org has SRV record 1 10 80 ec2-eu-west-1.portsnap.freebsd.org. _http._tcp.portsnap.FreeBSD.org has SRV record 4 10 80 ec2-ap-northeast-1.portsnap.freebsd.org. _http._tcp.portsnap.FreeBSD.org has SRV record 3 10 80 isc.portsnap.freebsd.org. _http._tcp.portsnap.FreeBSD.org has SRV record 2 10 80 sourcefire.portsnap.freebsd.org. _http._tcp.portsnap.FreeBSD.org has SRV record 4 10 80 ec2-sa-east-1.portsnap.freebsd.org. In the first case, one of the authoritative servers for the portsnap.freebsd.org domain was used. In the second case, the local BIND *the one from the dns/bind99 port) was used. The latter seems to preserve the case, the former does not. I'm not sure at what point the case conversion happens exactly. But that doesn't really matter. As I wrote earlier, DNS names are generally case-insensitive, so matching must be done in a case-insensitive way. Best regards Oliver