Re: What happened to nslookup?
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-unsubscr...@freebsd.org
Re: What happened to nslookup?
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-unsubscr...@freebsd.org Bind 10 requires python. There is a good reason it was removed from base. -- Allan Jude ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: What happened to nslookup?
On Wed, 16 Oct 2013, 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 version of nslookup on FreeBSD systems I've used had no command line history or editing (even ntpdc has this now), gave results that were not always in line with other tools (ldns, drill, host etc.), and to do a host lookup inside the nslookup shell you had to type ... host :-) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: What happened to nslookup?
On Sun, Oct 13, 2013 at 5:47 PM, Julian Elischer jul...@freebsd.org wrote:
On 10/12/13 10:28 AM, David Wolfskill wrote:
On Sat, Oct 12, 2013 at 02:14:28AM +, 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: rkober...@gmail.com
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: What happened to nslookup?
On 10/12/13 10:28 AM, David Wolfskill wrote:
On Sat, Oct 12, 2013 at 02:14:28AM +, 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
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
What happened to nslookup?
I thought I sent this message yesterday, but couldn't find it in the downloaded list messages, so maybe I forgot. Whatever happened to /usr/bin/nslookup in FreeBSD-current, and what is one supposed to use in its place? I see nslookup is in FreeBSD 9.2, but why not in -current? There has been plenty of dispute in recent days on removing rcs from base, subsequently resolved in keeping rcs, but no publicity on removing nslookup. There was no reference to nslookup in $SRCDIR/UPDATING for FreeBSD-current. I looked in $SRCDIR/usr.bin for both 9.2 and current, and nslookup was in 9.2 but not current. Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: What happened to nslookup?
On Fri, Oct 11, 2013 at 10:10:26PM +, Thomas Mueller wrote: ... Whatever happened to /usr/bin/nslookup in FreeBSD-current, and what is one supposed to use in its place? Use host. nslookup was part of BIND, and has been deprecated for years (IIRC). Peace, david -- David H. Wolfskill da...@catwhisker.org Taliban: Evil cowards with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpDxPU_b4umL.pgp Description: PGP signature
Re: What happened to nslookup?
On Fri, Oct 11, 2013 at 10:10:26PM +, Thomas Mueller wrote: ... Whatever happened to /usr/bin/nslookup in FreeBSD-current, and what is one supposed to use in its place? Use host. nslookup was part of BIND, and has been deprecated for years (IIRC). Peace, david -- David H. Wolfskill da...@catwhisker.org Thanks for info! I saw that bind was removed from the current branch because of security problems, 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? I will remember to use host in the future. Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: What happened to nslookup?
On Sat, Oct 12, 2013 at 02:14:28AM +, 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.
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
--
David H. Wolfskill da...@catwhisker.org
Taliban: Evil cowards with guns afraid of truth from a 14-year old girl.
See http://www.catwhisker.org/~david/publickey.gpg for my public key.
pgpMklaM0AE_U.pgp
Description: PGP signature
Re: What happened to nslookup?
On 10/11/2013 7:14 PM, Thomas Mueller wrote: On Fri, Oct 11, 2013 at 10:10:26PM +, Thomas Mueller wrote: ... Whatever happened to /usr/bin/nslookup in FreeBSD-current, and what is one supposed to use in its place? Use host. nslookup was part of BIND, and has been deprecated for years (IIRC). Peace, david -- David H. Wolfskill da...@catwhisker.org Thanks for info! I saw that bind was removed from the current branch because of security problems, but didn't know nslookup was part of BIND. That one caught me as well when I did make check-old with WITHOUT_BIND=YES. I installed dns/bind-tools to replace them (and got much newer versions in the process). ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
