On Sun, Aug 16, 2015 at 10:07 PM, Christian Kratzer <ck-li...@cksoft.de> wrote: > Hi, > > On Sun, 16 Aug 2015, Kurt Jaeger wrote: > <snipp/> >> >> We assumed that I have a DNS problem because of this line: >> >>> Looking up update.FreeBSD.org mirrors... none found. >> >> >> This happens with this query inside the freebsd-update script, at >> line 950: >> >> host -t srv _http._tcp.update.FreeBSD.org >> >> If you prime your DNS cache with manual queries, then freebsd-update >> will sometimes find the hosts and will report that it found some hosts. >> >> But, I just tried to reproduce this and failed, the problem persists. >> >> So, yes, it looks like a real issue. > > > hmmm. Thanks for pointing me at the dns issue. > > I actually did not see that message as it seems to only appear on > subsequent rounds of running freebsd-update. I always deleted > /var/db/freebsd-update and thus always started clean. > > I was able to complete the freebsd-update upgrade when I manually > specified on of the mirrors as in: > > freebsd-update -s update2.freebsd.org -r 10.2-RELEASE upgrade > > So this does seem to be a dns related issue. It could also be the > related to parsing the results of the dns lookup. > > Anyway seems we have a workaround if we specify the mirrors manually. > > Greetings > Christian > > --
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 The cure would be to use your own caching DNS resolver (configured to query the authoritative name servers directly) such as dns/unbound. -Kimmo _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
