From owner-freebsd-current@FreeBSD.ORG  Wed Oct 16 10:04:32 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 67B0384E
 for <freebsd-current@freebsd.org>; Wed, 16 Oct 2013 10:04:32 +0000 (UTC)
 (envelope-from daniel@digsys.bg)
Received: from smtp-sofia.digsys.bg (smtp-sofia.digsys.bg [193.68.21.123])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id E0D56210C
 for <freebsd-current@freebsd.org>; Wed, 16 Oct 2013 10:04:31 +0000 (UTC)
Received: from dcave.digsys.bg (dcave.digsys.bg [193.68.6.1])
 (authenticated bits=0)
 by smtp-sofia.digsys.bg (8.14.6/8.14.6) with ESMTP id r9G9ih4N090947
 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO)
 for <freebsd-current@freebsd.org>; Wed, 16 Oct 2013 12:44:44 +0300 (EEST)
 (envelope-from daniel@digsys.bg)
Message-ID: <525E600B.1010505@digsys.bg>
Date: Wed, 16 Oct 2013 12:44:43 +0300
From: Daniel Kalchev <daniel@digsys.bg>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: freebsd-current@freebsd.org
Subject: Re: What happened to nslookup?
References: <0E.82.01315.25778525@cdptpa-oedge03>
 <20131011221302.GH1611@albert.catwhisker.org>
 <54.9B.16944.480B8525@cdptpa-oedge02>
 <20131012022825.GJ1611@albert.catwhisker.org> <525B3F33.4030103@freebsd.org>
 <CAN6yY1urgs-YEZ-1CirWTCNtGf5g0Qd2pFuhjLST_9oPWZ=Pjg@mail.gmail.com>
In-Reply-To: <CAN6yY1urgs-YEZ-1CirWTCNtGf5g0Qd2pFuhjLST_9oPWZ=Pjg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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 10:04:32 -0000


On 16.10.13 08:42, Kevin Oberman 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.
>
> People should really use host(1) for simple lookups. It provides the same
> information and does it in a manner that will not cause misdirection when
> things are broken.

Of course, host(1) is not a replacement for nslookup(1).

nslookup is interactive, while host is not. This makes for a big 
difference in many usage scenarios.

The decision to remove bind from base was poor, and not well 
communicated. Let's hope it will be reverted.

Daniel