On Fri, Oct 29, 2004 at 11:09:39AM -0500, Adam Maloney wrote: > On Fri, 29 Oct 2004, Dan Rue wrote: > > >What exactly is not working? > > Initial problem was that he was having mail issues to itasca.net When he > said he was using ns.gofast.net and ns2.gofast.net, I asked both servers > and got different answers (ns.gofast.net failed for itasca.net, but > ns2.gofast.net worked correctly.) > > Try it: > > dig @ns.gofast.net itasca.net > > I get a SERVFAIL. But asking ns2 I get the correct answer. > > I (hesitantly) say it's an issue with ns.gofast.net, and pulling that out > of resolv.conf and using just ns2 should fix it. Yeah, it seems like it's a gofast.net problem - i ran doc (great dns utility) against itasca.net and it came up with 0 problems. Umm.. For a temporary fix, just use someone else's name server. Visi's are 209.98.98.98 and 208.42.42.42 It looks like they work from outside of visi.. And from Chris' mail: >My lesson for the day. That's good to know. I thought named might give >some benefit like faster lookups, but that benefit will be small. That's true - but it's usually a bad idea to compound problems by adding more variables :) Once you get this working, though, running a local bind will cache your dns for you, and in that configuration the setup is pretty easy. Tutorials exist everywhere.. dan _______________________________________________ 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