freebsd stable - Aug 2015 - freebsd-update to 10.2-RELEASE broken ?

> On 16 Aug 2015, at 21:16 , Christian Kratzer <ck-lists at cksoft.de>
wrote:
> 
> Hi,
> 
> On Sun, 16 Aug 2015, Kurt Jaeger wrote:
>> 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 ?
> 
> freebsd-update upgrade just failed on 3 other vm even when I explicitly
> specified the server using freebsd-update -s.
> 
> I had success on another vm when I changed to using google dns.
> 
> I am not aware that anything would be blocking tcp dns in my setups.
> 
> Must be something else dns related.
> 
> 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?


? 
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."

Hi!
> Or run tcpdump for port 53;   also curious if it might be an IPv4
> vs. IPv6 issue?
I did run tcpdump on port 53 on both the client and the
dns server for this, everything looked normal. It was no IPv6 issue.

I'll retest with more detail this evening.

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

> On 16 Aug 2015, at 23:08, Bjoern A. Zeeb <bzeeb-lists at
lists.zabbadoz.net> wrote:
> 
> 
>> On 16 Aug 2015, at 21:16 , Christian Kratzer <ck-lists at
cksoft.de> wrote:
>> 
>> Hi,
>> 
>> On Sun, 16 Aug 2015, Kurt Jaeger wrote:
>>> 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 ?
>> 
>> freebsd-update upgrade just failed on 3 other vm even when I explicitly
>> specified the server using freebsd-update -s.
>> 
>> I had success on another vm when I changed to using google dns.
>> 
>> I am not aware that anything would be blocking tcp dns in my setups.
>> 
>> Must be something else dns related.
>> 
>> 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?
I saw the issue on machines with IPv4/IPv6 and IPv4 only.
> ? 
> 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."
> 
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at
freebsd.org"

--
Bob Bishop          +44 (0)118 940 1243
rb at gid.co.uk    fax +44 (0)118 940 1295
             mobile +44 (0)783 626 4518