From owner-freebsd-stable Fri Jun 23 11:54:59 2000 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 932B337C40E for ; Fri, 23 Jun 2000 11:54:54 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id LAA10312; Fri, 23 Jun 2000 11:54:39 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <200006231854.LAA10312@freeway.dcfinc.com> Subject: Re: Weird NSLOOKUP output... In-Reply-To: from Brad Knowles at "Jun 23, 0 10:48:14 am" To: blk@skynet.be (Brad Knowles) Date: Fri, 23 Jun 2000 11:54:39 -0700 (MST) Cc: freebsd.stable@lists.craxx.nl, freebsd-stable@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Brad Knowles wrote: > I believe that dig & host both call the standard gethostbyname > routines, and therefore act in exactly the same way that a "normal" > program would, whereas nslookup would bypass any sort of service > switch you might have and instead go directly to the DNS. No. All three (dig, host and nslookup) use the resolver directly. I believe dig and host do call gethostbyname, but only when looking up the nameserver they're to use. You can prove it to yourself. Make an entry for a bogus host in /etc/hosts and then try to look it up. > It is my understanding that this is one of many reasons why nslookup > is so hated. Hated? Hmm... I kinda like it. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message