portsnap can't access portsnap[124].freebsd.org

[Glen Barber]

On Sat, May 30, 2009 at 12:48 AM, Scott Bennett <bennett at cs.niu.edu> wrote:
>>
>>Can you paste the 'ANSWER SECTON' from:
>>
>>  'dig portsnap2.freebsd.org'
>>
>     Sure, but I'm curious to know why.  The names all do resolve to A RRs,
> and pings to each by name did get echos back.  Here it is, although I did
> terminate the domain name by habit.  Surely portsnap must not be so silly
> as to pass unterminated names to the resolver.  (Actually, I'm including
> the whole output, not just the answer section.)
>

To make sure it wasn't a DNS problem (or DNS poisoning / hijacking).

>
> ;; ANSWER SECTION:
> portsnap2.freebsd.org.  3600    IN      A       72.21.59.250
>

Same output for me..


-- 
Glen Barber