You don't have to do anything with inetd. Inetd is only for setting up network access to programs that don't normally run as a daemon. You have your IN NS lines setup correctly and the SOA at the top of the config file? Does nslookup say "non-authoritative"? If not, it's considered authoritative. Keep in mind that you cannot give your DNS server a private address and NAT it to a public one. I've heard that you might be able to with Bind 9, but I haven't tried it. This doesn't sound like your problem, but keep that in mind. Jay > -----Original Message----- > From: Philip C Mendelsohn [mailto:mend0070 at tc.umn.edu] > Sent: Monday, January 15, 2001 10:58 PM > To: tclug-list at mn-linux.org > Subject: [TCLUG] BIND / named / inetd.conf > > > First time getting BIND going on the little net here, and I wonder if > anyone can answer a question for me. > > I think I have my zones and reverse lookups set up OK, but I get two > problems: > > 1: nslookup never tells me that I have an authoritative lookup. > 2: Sometimes things act funny -- i.e. dig says that it can't find > the server. > > Could this be that I don't have named set up in my > inetd.conf? It looks > to me like I don't. If that's it, do I have anything to > watch for when > setting a line up in inetd.conf? > > This is Debian potato, BTW. > > Cheers and thanks, > Phil M > > -- > "To misattribute a quote is unforgivable." --Anonymous > > _______________________________________________ > tclug-list mailing list > tclug-list at mn-linux.org > https://mailman.mn-linux.org/mailman/listinfo/tclug-list >