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.
Greetings
Christian
--
Christian Kratzer CK Software GmbH
Email: [email protected] Wildberger Weg 24/2
Phone: +49 7032 893 997 - 0 D-71126 Gaeufelden
Fax: +49 7032 893 997 - 9 HRB 245288, Amtsgericht Stuttgart
Mobile: +49 171 1947 843 Geschaeftsfuehrer: Christian Kratzer
Web: http://www.cksoft.de/
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[email protected]"
