Date: Wed, 16 Oct 2013 11:11:51 -0400 From: Lowell Gilbert <freebsd-current-local@be-well.ilk.org> To: Eitan Adler <lists@eitanadler.com> Cc: Kevin Oberman <rkoberman@gmail.com>, freebsd-current Current <freebsd-current@freebsd.org> Subject: Re: nslookup gave misleading results? Message-ID: <44a9i9l07c.fsf@be-well.ilk.org> In-Reply-To: <CAF6rxgmfF0%2B_FZ7zbzCNXJEVqRkpGdUnLpEjfm4sC6oaVFLJ2g@mail.gmail.com> (Eitan Adler's message of "Wed, 16 Oct 2013 10:28:45 -0400") References: <CAF6rxgmfF0%2B_FZ7zbzCNXJEVqRkpGdUnLpEjfm4sC6oaVFLJ2g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44a9i9l07c.fsf>