Date: Wed, 16 Oct 2013 12:44:43 +0300 From: Daniel Kalchev <daniel@digsys.bg> To: freebsd-current@freebsd.org Subject: Re: What happened to nslookup? Message-ID: <525E600B.1010505@digsys.bg> In-Reply-To: <CAN6yY1urgs-YEZ-1CirWTCNtGf5g0Qd2pFuhjLST_9oPWZ=Pjg@mail.gmail.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?525E600B.1010505>