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> In-Reply-To: <CA%2B7WWSdxf-YGn3cnD0H%2BSzj4yhvLS_XtB_qPZVkXabQbf=9u%2Bw@mail.gmail.com> 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%2B7WWSdxf-YGn3cnD0H%2BSzj4yhvLS_XtB_qPZVkXabQbf=9u%2Bw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150816200703.GN40589>