Chris,

Put just ns2.gofast.net's IP in resolv.conf - it should start working 
immediately.

As I stated, ns.gofast.net is returning SERVFAIL for itasca.net.  ns2 is 
not.  Just use ns2.  Then maybe e-mail GoFast's support and ask if they 
can look into the issue.

On Fri, 29 Oct 2004, Chris Schumann wrote:
>
> That comes back immediately with just 209.46.63.1 in my resolv.conf
> (ns.gofast.net). If I add 207.195.213.5 and -.6, it takes a while longer
> but returns the same result. (Those two IP's are listed as the domain
> hosts in whois itasca.net.)
>
> Adding 209.46.63.6 (ns2.gofast.net) makes it take longer but still fails.
>
> If I dig itasca.net, I get SERVFAIL with 209.46.63.1. If I use any of the
> other three IP's, I get timeouts.
>
> Chris Schumann
>
>
>
> _______________________________________________
> TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
> Help beta test TCLUG's potential new home: http://plone.mn-linux.org
> Got pictures for TCLUG? Beta test http://plone.mn-linux.org/gallery
> tclug-list at mn-linux.org
> https://mailman.real-time.com/mailman/listinfo/tclug-list
>

_______________________________________________
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
Help beta test TCLUG's potential new home: http://plone.mn-linux.org
Got pictures for TCLUG? Beta test http://plone.mn-linux.org/gallery
tclug-list at mn-linux.org
https://mailman.real-time.com/mailman/listinfo/tclug-list