From owner-freebsd-current@FreeBSD.ORG Wed Oct 16 15:14:24 2013 Return-Path: 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 C003B2F7 for ; Wed, 16 Oct 2013 15:14:24 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 9AE4525C9 for ; Wed, 16 Oct 2013 15:14:24 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 56DED3F264 for ; Wed, 16 Oct 2013 15:14:20 +0000 (UTC) Message-ID: <525EAD4C.10701@allanjude.com> Date: Wed, 16 Oct 2013 11:14:20 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; 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> <525E600B.1010505@digsys.bg> In-Reply-To: <525E600B.1010505@digsys.bg> Content-Type: text/plain; charset=ISO-8859-1 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Oct 2013 15:14:24 -0000 On 2013-10-16 05:44, Daniel Kalchev wrote: > > 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 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" Bind 10 requires python. There is a good reason it was removed from base. -- Allan Jude