Date: Sat, 28 Feb 1998 21:15:59 -0800 From: Studded <Studded@san.rr.com> To: Javier Henderson <javier@kjsl.com> Cc: Greg Lehey <grog@lemis.com>, "Tim O'Neil" <toniel@flash.net>, questions@FreeBSD.ORG, Frank McConnell <fmc@reanimators.org> Subject: nslookup sucks potatoes (Was: need more net hints) Message-ID: <34F8EF0F.BBC132BC@san.rr.com> References: <Your <199803010229.VAA01614@lakes.dignus.com> <199803010234.SAA10825@rah.star-gate.com> <3.0.3.32.19980228194430.00b2ece0@pop.flash.net> <19980301144341.01849@freebie.lemis.com> <199803010428.UAA17967@kjsl.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Javier Henderson wrote: > > Greg Lehey writes: > > On Sat, 28 February 1998 at 19:44:30 -0800, Tim O'Neil wrote: > > > I was wondering what exactly was meant when nslookup > > > reports "*** Can't find server for address 10.0.0.1: No > > > response from server. > > > > This one means that there is no reverse lookup for network 10. > > I respectfully disagree, and submit that resolv.conf is > pointing the resolver to 10.0.0.1, and named is not running on > that system (presumably the local host). Actually (and with all due respect) this is the infamous "nslookup sucks" error. :) This happens when you set up named on a system and put 'nameserver 10.0.0.1' in /etc/resolv.conf without setting up a reverse file for that address. For some odd reason nslookup won't function properly if it can't find a hostname for the IP address of the nameserver you're trying to use. There are several ways to solve this problem, fortunately they aren't tough to do. The canonical way to set up a local nameserver is to put 'nameserver 127.0.0.1' as the first entry in /etc/resolv.conf, IF you use that file. If you're only using one server and it's local (on the same machine), it's not necessary. There is a script to create a reverse file for the loopback address in /etc/namedb (make-localhost). You should run that script to generate the zone file and add it to the list of primary zones in /etc/named.boot. If you need the nameserver to listen on 10.0.0.1 for some reason, you should create a reverse file for that zone using the one created for localhost as a model and put that in as a primary in /etc/named.boot. You shouldn't need the root zone for any of this. You should probably fix up the localhost zone anyway, but you can also avoid some of these problems by using dig instead of nslookup. :) Hope this helps, Doug -- *** Chief Operations Officer, DALnet IRC network *** *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 5,328 clients and still growing. *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?34F8EF0F.BBC132BC>