From owner-freebsd-stable@freebsd.org  Sun Aug 16 20:07:02 2015
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 30C779BBB5C
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Sun, 16 Aug 2015 20:07:02 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id E68F0149C
 for <freebsd-stable@freebsd.org>; Sun, 16 Aug 2015 20:07:01 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: from pi by home.opsec.eu with local (Exim 4.86 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1ZR4Ct-000JcB-Ba; Sun, 16 Aug 2015 22:07:03 +0200
Date: Sun, 16 Aug 2015 22:07:03 +0200
From: Kurt Jaeger <lists@opsec.eu>
To: Kimmo Paasiala <kpaasial@gmail.com>
Cc: Christian Kratzer <ck@cksoft.de>,
 "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>
Subject: Re: freebsd-update to 10.2-RELEASE broken ?
Message-ID: <20150816200703.GN40589@home.opsec.eu>
References: <alpine.BSF.2.20.1508161911450.49345@noc1.cksoft.de>
 <2C3CC22D-749A-4B92-885C-D73311997050@gid.co.uk>
 <20150816180715.GM40589@home.opsec.eu>
 <alpine.BSF.2.20.1508162103400.49345@noc1.cksoft.de>
 <CA+7WWSdxf-YGn3cnD0H+Szj4yhvLS_XtB_qPZVkXabQbf=9u+w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+7WWSdxf-YGn3cnD0H+Szj4yhvLS_XtB_qPZVkXabQbf=9u+w@mail.gmail.com>
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Aug 2015 20:07:02 -0000

Hi!

> It could be the classic fall back to TCP on SRV records problem on
> your upstream DNS forwarder if you're using one:
> 
> http://lists.freebsd.org/pipermail/freebsd-ports/2012-May/074801.html

If I query that same DNS resolver using the line from
the script, it works every time. It's a 10.1p16 host with
a very recent ports build, and directly connected (no NAT, no
fw etc).

If that would be the problem, how could I diagnose it in depth ?

-- 
pi@opsec.eu            +49 171 3101372                         5 years to go !