From owner-freebsd-stable@freebsd.org Mon Aug 17 12:11:03 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 9F8DB9B9510 for ; Mon, 17 Aug 2015 12:11:03 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from mx0.gid.co.uk (mx0.gid.co.uk [194.32.164.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2E0F5190F for ; Mon, 17 Aug 2015 12:11:02 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from [194.32.164.24] (80-46-130-69.static.dsl.as9105.com [80.46.130.69]) by mx0.gid.co.uk (8.14.2/8.14.2) with ESMTP id t7HCAuBi010123; Mon, 17 Aug 2015 13:10:57 +0100 (BST) (envelope-from rb@gid.co.uk) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: freebsd-update to 10.2-RELEASE broken ? From: Bob Bishop In-Reply-To: Date: Mon, 17 Aug 2015 13:10:51 +0100 Cc: Christian Kratzer , "freebsd-stable@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <37B04206-8CC2-4FD5-BF11-19073BAAC36C@gid.co.uk> References: <2C3CC22D-749A-4B92-885C-D73311997050@gid.co.uk> <20150816180715.GM40589@home.opsec.eu> <20150816200703.GN40589@home.opsec.eu> To: "Bjoern A. Zeeb" X-Mailer: Apple Mail (2.2104) 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: Mon, 17 Aug 2015 12:11:03 -0000 > On 16 Aug 2015, at 23:08, Bjoern A. Zeeb = wrote: >=20 >=20 >> 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. >=20 > Or run tcpdump for port 53; also curious if it might be an IPv4 vs. = IPv6 issue? I saw the issue on machines with IPv4/IPv6 and IPv4 only. > =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." >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" -- Bob Bishop +44 (0)118 940 1243 rb@gid.co.uk fax +44 (0)118 940 1295 mobile +44 (0)783 626 4518