Response of *.freebsd.org websites are very slow

[Daniel Nebdal]

On Wed, Feb 27, 2013 at 3:28 PM, Mehmet Erol Sanliturk
<m.e.sanliturk at gmail.com> wrote:
>
>
> On Wed, Feb 27, 2013 at 6:22 AM, Daniel Nebdal <dnebdal at gmail.com> wrote:
>>
>> Ok, that's weird. What does a simple "nslookup ftp.freebsd.org" give you?
>>
>> On Wed, Feb 27, 2013 at 3:11 PM, Mehmet Erol Sanliturk
>> <m.e.sanliturk at gmail.com> wrote:
>> > On Wed, Feb 27, 2013 at 2:37 AM, Daniel Kalchev <daniel at digsys.bg>
>> > wrote:
>> >
>> >>
>> >>
>> >> On 27.02.13 12:23, Daniel Nebdal wrote:
>> >>
>> >>> I think you're supposed to be automatically sent to the mirror that is
>> >>> closest to you - for some value of "closest". If the mirror you're
>> >>> getting has issues, that might show up like this. Could you post the
>> >>> output of "traceroute ftp.freebsd.org" ? It should show which mirror
>> >>> you're getting, and perhaps if there are any obvious problems on the
>> >>> way.
>> >>>
>> >>
>> >> I believe, in his case that would be "traceroute ftp.tr.freebsd.org".
>> >> The
>> >> list of mirrors is here http://www.freebsd.org/doc/**
>> >>
>> >> handbook/mirrors-ftp.html<http://www.freebsd.org/doc/handbook/mirrors-ftp.html>
>> >>
>> >> in any case, "anything *.freebsd.org" actually refers to plenty of
>> >> hosts
>> >> all over the world -- some might be slow, some very fast.
>> >>
>> >> On the other hand, "Address could not be found" type of errors
>> >> indicates
>> >> something else than "fast" or "slow".
>> >>
>> >> Daniel
>> >>
>> >
>> >
>> > "traceroute ftp.tr.freebsd.org"
>> >
>> > is working .
>> >
>> >
>> > "traceroute ftp.freebsd.org <http://ftp.tr.freebsd.org>"
>> >
>> > is NOT working .
>> >
>> >
>
>
>
> nslookup ftp.freebsd.org
>
> ;; connection timed out ; trying next origin
> ;; connection timed out ; no servers could be reached
>
>
>
> netbsd , openbsd , dragonflybsd is working .
> ftp.tr.freebsd.org is working .
>
>
>
>
>
>>
>> > Thank you very much .
>> >
>> > Mehmet Erol Sanliturk
>> >

So nslookup (of ftp.freeebsd.org) fails on FreeBSD, but not the other
BSDs? That's very strange. Is /etc/resolv.conf the same in FreeBSD and
one of the working ones? Have you set up a firewall on the FreeBSD
install? Does it have IPv6?

--
Daniel Nebdal