From owner-freebsd-stable@freebsd.org Sun Aug 16 22:09:04 2015 Return-Path: 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 279A89BBF7E for ; Sun, 16 Aug 2015 22:09:04 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:130:3ffc::401:25]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D6D111328 for ; Sun, 16 Aug 2015 22:09:03 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id DC4FA25D3892; Sun, 16 Aug 2015 22:08:59 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 35451C7704A; Sun, 16 Aug 2015 22:08:59 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id 9of2IMoj1HbX; Sun, 16 Aug 2015 22:08:57 +0000 (UTC) Received: from [IPv6:fde9:577b:c1a9:4410:c13c:1353:3ca0:53b6] (unknown [IPv6:fde9:577b:c1a9:4410:c13c:1353:3ca0:53b6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 99993C76FCE; Sun, 16 Aug 2015 22:08:56 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\)) Subject: Re: freebsd-update to 10.2-RELEASE broken ? From: "Bjoern A. Zeeb" In-Reply-To: Date: Sun, 16 Aug 2015 22:08:53 +0000 Cc: "freebsd-stable@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: References: <2C3CC22D-749A-4B92-885C-D73311997050@gid.co.uk> <20150816180715.GM40589@home.opsec.eu> <20150816200703.GN40589@home.opsec.eu> To: Christian Kratzer X-Mailer: Apple Mail (2.2102) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Aug 2015 22:09:04 -0000 > On 16 Aug 2015, at 21:16 , Christian Kratzer = wrote: >=20 > Hi, >=20 > On Sun, 16 Aug 2015, Kurt Jaeger wrote: >> Hi! >>=20 >>> It could be the classic fall back to TCP on SRV records problem on >>> your upstream DNS forwarder if you're using one: >>>=20 >>> = http://lists.freebsd.org/pipermail/freebsd-ports/2012-May/074801.html >>=20 >> 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). >>=20 >> If that would be the problem, how could I diagnose it in depth ? >=20 > freebsd-update upgrade just failed on 3 other vm even when I = explicitly > specified the server using freebsd-update -s. >=20 > I had success on another vm when I changed to using google dns. >=20 > I am not aware that anything would be blocking tcp dns in my setups. >=20 > Must be something else dns related. >=20 > Perhaps I will run a local resolver in a vm and logg all queries and = dns > traffic. Or run tcpdump for port 53; also curious if it might be an IPv4 vs. = IPv6 issue? =E2=80=94=20 Bjoern A. Zeeb Charles Haddon Spurgeon: "Friendship is one of the sweetest joys of life. Many might have failed beneath the bitterness of their trial had they not found a friend."