Alright, what's going on here? Is there a router between your machine and itasca.net that could be filtering out that specific network prefix? Why not try adding a specific entry to your router's routing table? For example: ip route add 207.195.213.6/24 dev eth0 >> From: Adam Maloney <adam at whee.org> > >> Put just ns2.gofast.net's IP in resolv.conf - it should start working >> immediately. > > Yeah. It should, but doesn't. > >> 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. > > ns1.gofast.net does indeed return SERVFAIL here. > > ns2 is not returning SERVFAIL here. It times out, as does rocky and > bullwinkle (DNS of record for Itasca) as does Visi's DNS. > > My ISP is iagmn.net who uses gofast (I'm four hops to ns.gofast.net). > > Other ideas? > > 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