209.46.63.1 is Gofast. su-2.05b# dig @ns.gofast.net itasca.net ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 17181 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUERY SECTION: ;; itasca.net, type = A, class = IN Fails! But then, check this out: su-2.05b# dig @ns2.gofast.net itasca.net ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51264 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0 ;; QUERY SECTION: ;; itasca.net, type = A, class = IN ;; ANSWER SECTION: itasca.net. 1D IN A 207.195.213.6 ;; AUTHORITY SECTION: itasca.net. 1D IN NS bullwinkle.itasca.net. itasca.net. 1D IN NS rocky.itasca.net. ns.gofast.net fails but ns2.gofast.net works. Do you connect to Gofast or Agility? Temporary workaround is to use ns2.gofast.net / 209.46.63.6, but it may be nice to inform Agility of the discrepancy. It's possible that they don't intend you to use ns.gofast.net as a resolver (maybe recursion is off?)...many ISP's have name servers that serve auth information for their domains, and seperate resolvers for customers to use for DNS resolution. I can't say what Agility is doing, but if you're their customer, it may be worth asking their support. On Tue, 26 Oct 2004, Chris Schumann wrote: > Thanks for all the tips so far, folks. > >> Date: Tue, 26 Oct 2004 12:41:37 -0500 >> From: Brian Wall <kc0iog at gmail.com> > >> ping itasca.net >> dig itasca.net > >> <cschumann at twp-llc.com> wrote: >>> time. There's a set of domains (itasca.net) that I cannot send e-mail >>> to. > > ping: > [chris at alpha chris]$ ping itasca.net > ping: unknown host itasca.net > > dig: > [chris at alpha chris]$ dig itasca.net > > ; <<>> DiG 9.2.1 <<>> itasca.net > ;; global options: printcmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 20960 > ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 > > ;; QUESTION SECTION: > ;itasca.net. IN A > > ;; Query time: 18 msec > ;; SERVER: 209.46.63.1#53(209.46.63.1) > ;; WHEN: Tue Oct 26 13:14:49 2004 > ;; MSG SIZE rcvd: 28 > > lynx http://itasca.net: > Unable to locate remote host itasca.net. > >> From: "Garrett Krueger" <gkrueger at cleosci.com> >> I'd try /var/log/messages for a start. > Maybe later. > >> Another option is: service named status > No output at all. A clue! It must be using my upstream DNS for everything. > > And finally (Thanks Adam): > [chris at alpha chris]$ cat /etc/resolv.conf > nameserver 209.46.63.1 > > I forget who that is. > > What's my next step? > > Thanks again, > 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