From owner-freebsd-current@FreeBSD.ORG Wed Oct 16 05:42:18 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 41FB498C; Wed, 16 Oct 2013 05:42:18 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 13D6E21DE; Wed, 16 Oct 2013 05:42:18 +0000 (UTC) Received: by mail-pa0-f48.google.com with SMTP id bj1so538006pad.35 for ; Tue, 15 Oct 2013 22:42:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=nVe32dZ/C9Rt5zHqCky1HsIGL0BzLQF0RnfMNqmbrBk=; b=w0Kg0rO0a17AOHRPfvwloK0/FkJXiRyAuGJvgy/GOlZnaPfgHKzdASWDK0Gcqz/4fJ vbsh66dmblNLEt0DRORlV1G8QONV5COYX4CkOLB3Nsof4izS5TJJEU9sZ+En0ZsAB9Uo j28tdVLPjcqB/XHFz9ysQ54xAS7/PZ7jChs7z+CHjQ9W8e93h3izf9e6XxXqkOEQLxom CUF9KqC889lM7sHggkojhZcP19bpfruMj0OsuYPXhX0xD1cHvobThgzbKY3jNMeEETgn krKscCKrPaKUp0pY6PlQzlJV9KwU0PdJteQf2KBBnuICZO+Gyu0zqnOzMFrdaf0chz0V tPRA== MIME-Version: 1.0 X-Received: by 10.66.66.42 with SMTP id c10mr1683855pat.98.1381902137600; Tue, 15 Oct 2013 22:42:17 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.67.23.101 with HTTP; Tue, 15 Oct 2013 22:42:17 -0700 (PDT) In-Reply-To: <525B3F33.4030103@freebsd.org> 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> Date: Tue, 15 Oct 2013 22:42:17 -0700 X-Google-Sender-Auth: 27xeB266SYCOjbId3w0UeDgLi6A Message-ID: Subject: Re: What happened to nslookup? From: Kevin Oberman To: Julian Elischer Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Current 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 05:42:18 -0000 On Sun, Oct 13, 2013 at 5:47 PM, Julian Elischer wrote: > On 10/12/13 10:28 AM, David Wolfskill wrote: > >> On Sat, Oct 12, 2013 at 02:14:28AM +0000, Thomas Mueller wrote: >> >>> ... >>> Thanks for info! >>> >> Glad to help. >> >> I saw that bind was removed from the current branch because of security >>> problems, >>> >> It was removed, but I believe that there was a bit more to it than >> "security problems." >> > I think it was just a personal preference that managed to get communicated > as "important", and no-one had the energy or will to argue about it. > (that's the way software projects often work.. loudest and most persistent > voice wins). > > > but didn't know nslookup was part of BIND. >>> >>> Now I see in $PORTSDIR/dns/bind-tools/pkg-**plist >>> >>> bin/dig >>> bin/host >>> bin/nslookup >>> >>> so host is also part of BIND? >>> >> :-} The version of host we had when BIND was part of base was part of >> BIND, yes. Looking in src/usr.bin/host/Makefile, I see: >> >> # $FreeBSD: head/usr.bin/host/Makefile 255949 2013-09-30 17:23:45Z des $ >> >> LDNSDIR= ${.CURDIR}/../../contrib/ldns >> LDNSHOSTDIR= ${.CURDIR}/../../contrib/ldns-**host >> ... >> >> which indicates that this is a re-implementation of "host" as >> provided by contrib/ldns. >> >> I will remember to use "host" in the future. >>> >> I have found it generally easy to use (easier by far than nslookup). >> >> Peace, >> david >> > > 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. If you REALLY want to dig (sorry) into DNS behavior or problems, learn to use dig(1). It does the same as host(1) or nslookup(1) in it's simplest form but has an extremely large number of options to adjust the query in a variety of ways to allow real analysis of DNS behavior. I'd love to see nslookup simply vanish, but I expect it to be around and causing grief until the day I die (which I hope will still e at least a couple of decades down the road.) -- R. Kevin Oberman, Network Engineer E-mail: rkoberman@gmail.com