From owner-freebsd-current@FreeBSD.ORG  Wed Oct 16 15:18:11 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 8D789463
 for <freebsd-current@freebsd.org>; Wed, 16 Oct 2013 15:18:11 +0000 (UTC)
 (envelope-from freebsd-current-local@be-well.ilk.org)
Received: from be-well.ilk.org (be-well.ilk.org [23.30.133.173])
 by mx1.freebsd.org (Postfix) with ESMTP id 6559625FC
 for <freebsd-current@freebsd.org>; Wed, 16 Oct 2013 15:18:11 +0000 (UTC)
Received: by be-well.ilk.org (Postfix, from userid 1147)
 id B5A4D33C49; Wed, 16 Oct 2013 11:11:51 -0400 (EDT)
From: Lowell Gilbert <freebsd-current-local@be-well.ilk.org>
To: Eitan Adler <lists@eitanadler.com>
Subject: Re: nslookup gave misleading results?
References: <CAF6rxgmfF0+_FZ7zbzCNXJEVqRkpGdUnLpEjfm4sC6oaVFLJ2g@mail.gmail.com>
Date: Wed, 16 Oct 2013 11:11:51 -0400
In-Reply-To: <CAF6rxgmfF0+_FZ7zbzCNXJEVqRkpGdUnLpEjfm4sC6oaVFLJ2g@mail.gmail.com>
 (Eitan Adler's message of "Wed, 16 Oct 2013 10:28:45 -0400")
Message-ID: <44a9i9l07c.fsf@be-well.ilk.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain
Cc: Kevin Oberman <rkoberman@gmail.com>,
 freebsd-current Current <freebsd-current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Oct 2013 15:18:11 -0000

Eitan Adler <lists@eitanadler.com> writes:

> On Wed, Oct 16, 2013 at 1:42 AM, Kevin Oberman <rkoberman@gmail.com> wrote:
>> nslookup(1) was deprecated about a decade ago because it often provides
>> misleading results when used for DNS troubleshooting. It generally works
>> fine for simply turning a name to an address or vice-versa.
>
> Can you give a bit more detail on this?  In what ways did it give
> misleading results?

A couple of different reasons cited by ISC for why they deprecated it a
long time ago:  nslookup bundled an internal resolver library, and so it
wouldn't always give the same results as other utilities. Also, it
always ignored some of the host configuration.

-- 
Lowell Gilbert